Re: Changing systemd startup timeout

[Curt <curty@free.fr>]

On 2018-05-16, Sven Joachim <svenjoac@gmx.de> wrote:
>>
>> # systemctl edit mysql
>> <add the setting using vim>
>> # systemctl show mysql -p TimeoutStartUSec
>> TimeoutStartUSec=1min 30s
>> # systemctl daemon-reload
>> # systemctl show mysql -p TimeoutStartUSec
>> TimeoutStartUSec=1min 30s
>> # systemctl daemon-reexec
>> # systemctl show mysql -p TimeoutStartUSec
>> TimeoutStartUSec=1min 30s
>>
>> What do I need to do to make this actually work?
>
> Have you tried setting TimeoutStartSec rather than TimeoutStartUSec?
> Though I have to admit that I did not perform a web search but cheated
> by looking at the systemd.service(5) manpage, which mentions the former
> but not the latter.

Moderately confusing to the hoi polloi because 'systemctl show' lists

 DefaultTimeoutStartUSec=1min 30s

here (and probably elsewhere).

It appears that the property and the configurable option are
unidentical. This could lead to head-scratching as well as unwelcome
headaches.

USECs are apparently µs (microseconds--dbus api unit). 

Anyway, it's all far beyond me, and your advice is sound. I was going to
say but didn't earlier that previously '0' (prior to systemd version
239) rather than 'infinity' turned off timeouts (not exactly what
you'd call intuitive, either, 0=infinity), in case the OP might be
using some older release.

> Cheers,
>        Sven
>
>


--