This probably got introduced with the fix for bug 1448259. So, this
general behaviour is "correct" in the sense that processes should not be
killed immediately after SIGTERMing them. But 90s is a bit much for
session shutdowns, this could be reduced to something like 30 s. This is
still a long session shutdown, but you really wan this if e. g.
LibreOffice asks you about unsaved documents and the like.
I don't know what the timeout under upstart was, but apparently it was a
lot smaller.
** Summary changed:
- linconnect_server.py hangs on shut down
+ reduce 90s session kill timeout if the session does not shutdown cleanly
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1457400
Title:
reduce 90s session kill timeout if the session does not shutdown
cleanly
Status in systemd package in Ubuntu:
Confirmed
Bug description:
I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
onwards the ubuntu is taking long to shut down nearly 1:30 minutes.
I checked the shutdown log messages and I get the follow message.
A stop job is running for Session c2 of user ***** (25s/ 1min 30 s)
It count downs till 1:30 minutes and then shutdown the machine.
Why is it happening.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
