<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - rc-local's TimeoutSec=0 cause shutdown to hang if rc.local spawned any daemons" href="https://bugs.freedesktop.org/show_bug.cgi?id=84110#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - rc-local's TimeoutSec=0 cause shutdown to hang if rc.local spawned any daemons" href="https://bugs.freedesktop.org/show_bug.cgi?id=84110">bug 84110</a> from <a class="email" href="mailto:xani666@gmail.com" title="XANi <xani666@gmail.com>"> XANi</a> <pre>(In reply to Lennart Poettering from <a href="show_bug.cgi?id=84110#c1">comment #1</a>) > We have to kill all daemons so that we can properly unmount the various file > systems, there isn't really a way around this. > > For compatibility with sysv we explicitly turn off the timeout, since that's > more like this worked on sysvinit (and rc-local is really just about compat > here, at least to the point where it doesn't interfere with other concepts). > > While we try to stay as compatible with sysvinit as we can, there are > limitations, this is one of them, this specific behaviour of sysvinit is > something that actively destabilizes the system on shutdown, hence I don't > think this is something we should change (we could change it, by doing > KillMode=none by default...) > > I hope that makes sense, > > Sorry! The problem is a bit different and not only rc.local (which I admit should definitely not be a place to start random daemons), if that ( or any other daemon that do not have timeout set and "hangs" ) stops system from rebooting/halting, a number of situations might happen, all of which worse than killing random daemon like: * UPS got 5-10 minutes of battery left, if system does not umount = power off without unmouting/remounting ro. And fsck on 1TB partition. * Someone is logged in remotely, types "reboot" and exits. He can't ssh back to fix it (because SSH daemon already shut down), not everyone have KVM so only option is to hard reboot via remote power or drive to reboot machine. * Type "poweroff" on laptop and put it into a backpack, dead battery in few hours What I am saying is that in a lot of cases not being able to reboot system in decent time (5-10 minutes) can potentiall have much greater consequences than sending sigkill to to some random daemon</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>