[systemd-devel] hanging reboot
sergei.franco at gmail.com
Thu Mar 30 23:07:40 UTC 2017
Thank you very much!
It just shows that I was never patient enough to actually test it long
enough to hit 30min timeout (after about 15 min I generally would reset the
The JobTimeoutSec is a good candidate to be reduced to something like 5 min
for our use case.
On 31 March 2017 at 05:52, Lennart Poettering <lennart at poettering.net>
> On Thu, 09.03.17 13:00, Sergei Franco (sergei.franco at gmail.com) wrote:
> > Hello!
> > Thank you very much for pointing out the "After" vs "Before", as in for
> > ExecStop to run Before filesytem is unmounted it must be configured as
> > After :).
> > This fixes the Ubuntu unattended upgrades unit that prevents from
> > What I would like to address for future problems like this is how to
> have a
> > global timeout where systemd gives up and reboots anyway (regardless the
> > state of the units)? Even if it is a dirty reboot.
> We have that in place. It's configured to 30min however, in order to
> be friendly to super-slow databases.
> See "systemctl cat reboot.target":
> Lennart Poettering, Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the systemd-devel