[systemd-devel] My experience with MySQL and systemctl
Auke Kok
auke-jan.h.kok at intel.com
Thu Apr 13 20:07:57 UTC 2017
On 04/13/2017 02:48 AM, Lennart Poettering wrote:
> On Wed, 12.04.17 21:09, Michael Biebl (mbiebl at gmail.com) wrote:
>
>> 2017-04-12 20:24 GMT+02:00 Tomasz Torcz <tomek at pipebreaker.pl>:
>>> On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote:
>>>> The right (or, better) solution IMHO would be for mysqld to signal to
>>>> systemd that it's running OK before recovery starts, using type=notify.
>>>> This way recovery can take as long as needed, and if it fails, it could
>>>> signal this failure as normal back to systemd. Then systemd would retry
>>>> the recovery a few times this way and finally give up.
>>>
>>> It wouldn't be good solution. READY=1 means clients can connect and
>>> talk to the database. Signalling readiness prematurely would break functionality..
>>
>> 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.
>
> There was an RFE somewhere for supporting watchdog messages
> (i.e. WATCHDOG=1) during startup too, not just during runtime. I'd be
> fine with adding that.
that sounds more than reasonable, +1
Auke
More information about the systemd-devel
mailing list