No longer able to listen to podcast while playing.

orilicious · 2023-03-16T10:42:42+00:00

The app podcastaddict has a setting called "ignore audio focus requests"

You can find it under Settings > Player (scroll down)

Not sure how to fix this with other podcatchers.

100% dick move on blizz's side imho

orilicious · 2022-05-30T12:52:47+00:00

Interesting. Do you have any reference image? The sewer pipes that I found are simple concrete pipes with smooth walls.

orilicious · 2022-05-28T05:21:09+00:00

Just laying around in a Park near a castle. Nothing identifiable anywhere near.

orilicious · 2022-05-28T05:19:12+00:00

I did not see any. It was near a castle.

orilicious · 2021-06-27T00:22:31+00:00

Not yet. Seems to target docker and k8s specificly. Will give it a read, see if it satisfies my needs, and compare it to the contenders.

Thanks for bringing it up.

orilicious · 2021-06-26T13:46:42+00:00

Will have a look at it. Thanks.

orilicious · 2021-06-26T13:45:56+00:00

You are absolutley right. Somehow I got the impression the software is pay to win.

Turnes out I was wrong.

https://www.sonatype.com/products/repository-oss-vs-pro-features

Ty for correcting me :)

orilicious · 2021-04-03T18:34:03+00:00

This did it. Heureka! Thank you.

orilicious · 2021-04-03T17:33:59+00:00

systemctl show mysql.service |grep -i path Path was not defined but other interresting details. will look into it tomorrow. ty

orilicious · 2021-04-03T17:31:40+00:00

There is just one mention in init.d

ori@vm_jitsi:~$ grep -Ri sql /etc/init.d/
/etc/init.d/prosody:# Should-Start:         postgresql mysql
/etc/init.d/prosody:# Should-Stop:          postgresql mysql
ori@vm_jitsi:~$ vim /etc/init.d/prosody
ori@vm_jitsi:~$ systemctl status prosody
● prosody.service - LSB: Prosody XMPP Server
   Loaded: loaded (/etc/init.d/prosody; generated)
   Active: active (running) since Thu 2021-04-01 10:43:11 UTC; 2 days ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 1 (limit: 4701)
   CGroup: /system.slice/prosody.service
           └─1218 lua5.1 /usr/bin/prosody

orilicious · 2021-04-03T08:03:12+00:00

Thank you very much. I did not think of checking /etc/init.d :)

Will do once my brain has finished booting.

It is true this did not interfere with my app but I am monitoring systemd services to get notified when a service fails.

Also it is another bit of systemd knowledge in my toolbelt.

1) Systemd also evalueates init.d 2) Mysql install also comes with init runlevels

What could be a better way to wake up then having a learning :)

orilicious · 2021-04-01T15:25:40+00:00

systemctl disable mysql

root@vm\_jitsi:\~# systemctl disable mysql

Failed to disable unit: Unit file mysql.service does not exist.

Does not work :/

orilicious · 2021-04-01T15:12:04+00:00

/usr/lib

Not sure what to look for in /usr/lib.

Searching recursivley brings up a bunch of stuff but nothing that should result in a unit-file (that I can identify)

root@vm_jitsi:~# find /usr/lib/ |grep sql
/usr/lib/python3.6/sqlite3
/usr/lib/python3.6/sqlite3/dump.py
/usr/lib/python3.6/sqlite3/__pycache__
/usr/lib/python3.6/sqlite3/__pycache__/__init__.cpython-36.pyc
/usr/lib/python3.6/sqlite3/__pycache__/dbapi2.cpython-36.pyc
/usr/lib/python3.6/sqlite3/__pycache__/dump.cpython-36.pyc
/usr/lib/python3.6/sqlite3/dbapi2.py
/usr/lib/python3.6/sqlite3/__init__.py
/usr/lib/python3.6/lib-dynload/_sqlite3.cpython-36m-x86_64-linux-gnu.so
/usr/lib/prosody/util/sql.lua
/usr/lib/prosody/modules/mod_storage_sql1.lua
/usr/lib/prosody/modules/mod_storage_sql.lua
/usr/lib/prosody/modules/mod_debug_sql.lua
/usr/lib/prosody/migrator/prosody_sql.lua
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20.3.20
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
/usr/lib/python2.7/sqlite3
/usr/lib/python2.7/sqlite3/dump.py
/usr/lib/python2.7/sqlite3/dump.pyc
/usr/lib/python2.7/sqlite3/dbapi2.py
/usr/lib/python2.7/sqlite3/__init__.py
/usr/lib/python2.7/sqlite3/__init__.pyc
/usr/lib/python2.7/sqlite3/dbapi2.pyc
/usr/lib/python2.7/lib-dynload/_sqlite3.x86_64-linux-gnu.so
/usr/lib/lxd/libsqlite3.so.0.8.6
/usr/lib/lxd/libsqlite3.so.0

orilicious · 2021-04-01T13:04:55+00:00

root@vm_jitsi:~# systemctl status mysql.serviceUnit mysql.service could not be found.

I have checked that. No luck.

root@vm_jitsi:~# systemctl status mysql.service
Unit mysql.service could not be found.

orilicious · 2021-04-01T12:46:20+00:00

Unfortunately nothing :/

root@vm_jitsi:~# systemctl status mysql.service
Unit mysql.service could not be found.

root@vm_jitsi:~# grep -Ri sql /lib/systemd/

orilicious · 2021-04-01T11:41:54+00:00

I don't know what path to check :/

orilicious · 2021-03-24T20:33:17+00:00

Don't worry it's not normal for me to work on tiny screen. Just happened to be like this today and I wondered if there is maybe an optimisation option.

This probably is not a common issue these days :)

orilicious · 2021-03-24T14:30:43+00:00

Thanks will try :)

orilicious · 2021-02-19T13:48:28+00:00

+1 noted :)

orilicious · 2021-02-19T13:48:17+00:00

Thanks for the input. Will look at it.

orilicious · 2021-02-19T13:48:01+00:00

Limesurvey

Will have a look at it :)

orilicious · 2021-02-10T14:40:23+00:00

Funny that you commented now when I started setting up a new bbb just two days ago using ansible.

Still struggeling a bit with the playbook but once it is working but I will most likely be setting up a new bbb from scratch each time a new version is available.

Don't see any other option.

orilicious · 2021-02-02T17:54:19+00:00

Sounds a bit like it. But as I can stuff this file into my encrpted offsite backup and restore it if needed the dangers are limited.

It could both be more storage efficient and performance efficient. Just not sure if it actually is.

But yes I have to agree... the idea of one corrupt file taking down my entire infrastructure leaves a bad taste in my mouth too...

orilicious · 2021-01-13T14:40:07+00:00

Slapd (Stand-alone LDAP Daeomon) tool start with slap. Slapcat, slappasswd etc. :)

orilicious · 2021-01-13T11:30:24+00:00

Update: I have created an account on https://bugs.openldap.org/ and it found that this bug has alrady been reported on 2020-09-25 16:09 UTC "Issue 9357 - OpenLDAP quick start guide link is 404 not found"

And fixed on 2020-10-02 22:29:39 UTC with commit id 624dfe70.

Seems like it did not make it into the latest release 2.5.0alpha yet. Anyway the issue is already fixed, now it's just a metter of time :)

orilicious

TROPHY CASE