[systemd-devel] My experience with MySQL and systemctl

[Reindl Harald]

Am 13.04.2017 um 06:06 schrieb Andrei Borzenkov:
>> Maybe we'd need a new state paramenter, like STARTING=1 which could be
>> sent by the daemon to systemd in regular intervals and would signal
>> systemd that the startup of the daemon is in process and the daemon is
>> not actually hung.
> 
> You still need to upper bound it. Consider service that is run on
> shutdown. You cannot indefinitely wait for service that is stuck in
> STARTING state.
> 
> So STARTING state is marginally useful to catch hung service, but at
> some point service manager still needs to decide how long it wants to
> wait. We are back at square one.

why should a process at shutdown/stop signal "STARTING=1"?

you should at least distinct between STARTING/STOPPING and combine that 
with two different settings for the systemd-unit where can be specified 
how long in each of that states should be waited

that distributions and users should get rid of mysqld_safe to use that 
is a different story, we are probably the first which switched to a 
native systemd-unit in 2011 for all servers and i can assure nobody 
needs mysqld_safe at all