Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
"Systemd sometimes doesn't shutdown" -- collecting links and info
It's very sporadic, somewhat rare, so I won't really open a thread on the forums themselves, but I'll just collect links and snippets here hoping there's some way to fix it, if it doesn't get fixed "by itself"/by systemd/debian developers first.
I never tried the "-i" thing, though. It would be just a work-around, though, not really a fix.
It's hard to find seemingly relevant information. It seems behavior like this (or rebooting instead of shutting down) is quite common (I've found mostly bug reports/forum threads when googling just for "systemctl poweroff /sbin/poweroff", hoping to find if they were different things, but "file" told me the latter is a symlink). Some recommendations include purging packages I've never have installed, or silly things like calling the "systemctl poweroff" command via the /sbin/poweroff symlink to it, or vice-versa. It seems some people got the issue solved by half-reinstalling sysv...
_________________________
September 18, 2015 - it seems it doesn't happen anymore, for quite a while now. However, nowadays what happens sometimes (rarely) is that KDM auto-login will fail with a message with a keyword like "pam-nologin". I'll probably change from KDM to "slimDM" or whatever in the somewhat near future (until ssdm/whatever is the new plasma/former-kde dm becomes mandatory, if its config isn't compatible enough/similar enough with kdmrc or annoys me otherwise), so maybe it won't be a problem even if it persists.
Quote:
I have Mate desktop and Slim installed:
halt_cmd /sbin/systemctl poweroff -i
reboot_cmd /sbin/systemctl reboot -i
like this, when I request shutdown all applications exit and then slim restart and shutdown is stopped ?
However when I add --force to this command it looks like everything works; but is there a way to send SIGTERM and wait for all processes to end ? because with force they will be killed immediately with SIGKILL and won't wait for them.
First i thought some application suppressed shutdown so I added the -i to ignore all inhibitors but no luck.
Thanks in advance.
https://bbs.archlinux.org/viewtopic.php?id=175626
halt_cmd /sbin/systemctl poweroff -i
reboot_cmd /sbin/systemctl reboot -i
like this, when I request shutdown all applications exit and then slim restart and shutdown is stopped ?
However when I add --force to this command it looks like everything works; but is there a way to send SIGTERM and wait for all processes to end ? because with force they will be killed immediately with SIGKILL and won't wait for them.
First i thought some application suppressed shutdown so I added the -i to ignore all inhibitors but no luck.
Thanks in advance.
https://bbs.archlinux.org/viewtopic.php?id=175626
It's hard to find seemingly relevant information. It seems behavior like this (or rebooting instead of shutting down) is quite common (I've found mostly bug reports/forum threads when googling just for "systemctl poweroff /sbin/poweroff", hoping to find if they were different things, but "file" told me the latter is a symlink). Some recommendations include purging packages I've never have installed, or silly things like calling the "systemctl poweroff" command via the /sbin/poweroff symlink to it, or vice-versa. It seems some people got the issue solved by half-reinstalling sysv...
_________________________
September 18, 2015 - it seems it doesn't happen anymore, for quite a while now. However, nowadays what happens sometimes (rarely) is that KDM auto-login will fail with a message with a keyword like "pam-nologin". I'll probably change from KDM to "slimDM" or whatever in the somewhat near future (until ssdm/whatever is the new plasma/former-kde dm becomes mandatory, if its config isn't compatible enough/similar enough with kdmrc or annoys me otherwise), so maybe it won't be a problem even if it persists.
Total Comments 1
Comments
-
Eventually it ceased to occur, it seems. I wonder if everybody is still hating systemd as much or even more.Posted 06-25-2015 at 12:07 PM by the dsc 
