Guido U. Draheim

Is it expecting that the directory gets created by the service-manager? Please include "systemctl cat mysqld" and show the logs for "systemctl start mysqld -vvvv" My own tests did include...

It seems that systemctl.py has done its share, so one would need to inspect the mysql log what it was missing. I wonder why mysqld_pre_systemd needs to be run as...

By the way, PermissionsStartOnly is deprecated. systemd/systemd#10802:

For a "Type=notify" service the notify-socket is actually created. It waits for the READY=1 on each ExecStart before continuing. After it got that signal it will close the socket however....

2021-12-08 06:53:59,017 DEBUG okay, wating on socket for 0.0s 2021-12-08 06:53:59,018 INFO wait $NOTIFY_SOCKET, timeout 0.0 (lapse 3) 2021-12-08 06:54:00,018 INFO .... timeout while waiting for 'READY=1' status on $NOTIFY_SOCKET...

Well, that's not implemented. It seems nobody did try such a global non-timeout before.

Please compare #4 that simple options may take a while to get implemented. The systemd sphere has a ton of options that may take full-time-equivalents of years to get implemented...

> why is the socket closed at all? can it be kept alive so the services can dispatch the notifications regularly? The systemctl-replacement is very different from a systemd daemon...

The real systemctl has clear opinion on it: systemctl show [email protected] Failed to get properties: Unit name [email protected] is neither a valid invocation ID nor unit name. Therefore the template...

The message bus and systemd are actually two different hings. The systemd' systemctl will use the messagebus to lookup the connection to system which is otherwise using a unix domain...