Hit 7 times alt-ctrl-del, the shutdown will continue. On 07/25/2017 03:07 PM, Hans de Faber wrote:
Additional question:
Does anybody know where the waittime of this stopjobs is defined ?
Op 25-07-17 14:05, Peter Suetterlin schreef:
John Andersen wrote:
Today, I started seeing stop jobs taking too long on my 42.2 system. TBH, for this is one of the most annoying features of systemd: Quite sometimes I have issues like a forgotten login on another console, or a (manually mounted) NFS directory.
Then the reboot stops. Which is OK. BUT: You can do absolutely NOTHING. all login is already disabled, both on other ttys or via ssh. It's abolutely pointless to wait for something to happen that cures the issue.
As a consequence I've reduced the wait time for stop jobs...
For example Samba NMB counted down the entire 1:30 seconds before system[some letter we dare not mention] killed it. There are no actual stop job defined for nmb.service Sounds like a case similar to my NFS mount above - was there some remote samba access still active?
What is up with the stop jobs suddenly taking so long? I wasn't aware this was changed in any recent update. Haven't noticed this on my Leap systems, so I rather think there's something changed in your local (network) setup that is triggering it...
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org