Bonjour,
"a stop job is running for rc.local compatibility no limit"
This a new fantasy of systemd on my system when I shut it down and there is "no limit": after half a hour, the computer stops with this message: "forcibly powering off: job timed out".
This is boring!
Why this? I made no update, no change in my configuration which worked correctly...
What is this job? We cannot know... *A job* that's all we can know! Looking at the journal (journalctl -u rc-local) shows nothing wrong.
How to stop this weird behavior?
systemd was supposed to increase the speed, in fact since systemd replaced the previous system boot takes more time (30s instead of 10s if no "start job is running" occurs...) and I did not see any change in the speed of the computer.
Thank you.
On Wed, 5 Jun 2019 12:05:08 +0200 François Patte francois.patte@mi.parisdescartes.fr wrote:
"a stop job is running for rc.local compatibility no limit"
This a new fantasy of systemd on my system when I shut it down and there is "no limit": after half a hour, the computer stops with this message: "forcibly powering off: job timed out".
Do you start any jobs in /etc/rc.d/rc.local? These are jobs that you want started at boot, but aren't system jobs. Usually, it is an application that a user has built and installed themselves, but it can be anything.
If a stop job doesn't terminate, it usually means that the job it is trying to stop is in non-interruptable sleep, or does not catch SIGTERM signals, and so misses the SIGTERM sent to all running processes for shutdown.
I never had that error, but I had other rc.local problems which led me to do this:
/etc/rc.d/rc.local just looks like:
/usr/bin/at -M now <<'HERE' > /dev/null 2>&1 /etc/rc.d/the-real-rc.local HERE
touch /var/lock/subsys/local
Then /etc/rc.d/the-real-rc.local has all the stuff I used to put in rc.local itself. This starts everything outside the control of systemd, so it doesn't know what started and can't make any dreadful assumptions about what it should do with it.