John Andersen composed on 2017-07-21 11:58 (UTC-0700):
Today, I started seeing stop jobs taking too long on my 42.2 system.
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
The prior shutdown wanted to count down 5 minutes to shutdown modemmanager.service. (the service file shows no stop job defined). There's no configuration specifying a 5 minute timeout on anything.
(Side issue: why is modemmanager wanted by multiuser.target?)
If like most users you are on broadband behind a firewall/router, why is modemmanager even installed?
What is up with the stop jobs suddenly taking so long? I wasn't aware this was changed in any recent update.
I've often found that stop jobs delay shutdown on various installations. Figuring out exactly why I've never pursued, but NAICT it is a typical result of network start jobs that never took place that systemd thinks need stopping. NMB is one I particularly remember seeing far too often. Does 'umount -a' prior to attempting shutdown help? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org