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
I ran the command .
johny@johny-laptop:~$ pkill -fe linconnect_server.py
python2 killed (pid 2469)
But its not actually getting killed.
If I go to system monitor and see, the process is still there.
If I kill the process by right clicking it System monitor and pressing
kill. The process gets
** Summary changed:
- Ubuntu taking long to shutdown
+ linconnect_server.py hangs on shut down
--
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:
What happens at shutdown is that all processes are sent SIGTERM, so that
they have a chance to intercept, save their state/clean up, etc. After a
timeout (default 90s) SIGKILL is sent. So it seems linconnect_server.py
does not actually shut down on SIGTERM?
I tried to download and install it, but
4 matches
Mail list logo