Today I just learned that systemctl --force --force reboot is a command. We had a computer we remotely connected to which got permission errors and bus errors when we tried to reboot it normally. For some reason the mentioned command did actually manage to shutdown the computer bit did not manage to reboot it correctly.
I wonder what the double --force flag actually accomplishes and what possibly could hinder a regular reboot in this scenario.
I would use the man pages but my working laptop uses Windows and since the system died i dont have any way to check them until I get home.
Thank you a lot for the answer though, that does explain a lot!
honestly glad you made the thread still cause I just love questions like this to see if I can answer them and if I can’t I learn something
oftentimes (and this is more of a general statement) throwing into google exactly what you would otherwise type into your shell of choice should get you on the right track, ie searching for “man systemctl”
as far as the inability to reboot goes, if a regular
sudo rebootcan’t bring the machine back up either then this is probably a hardware issue outside the sphere of the operating system’s influence. can’t say I experienced something like that myself. I guess the closest I witnessed would be a computer that when rebooted with an old USB-Keyboard plugged in just refused to get past the POST screen. The keyboard worked fine if plugged in later, but the computer couldn’t reliably get through the boot process with the thing present. Maybe there’s a similar variable to your setup.Manpages.org
It sounds like it should be a hookup app, but it actually is the online Linux man pages.
Or, for a less dubious sounding site, man7.org
man7 and such are better. This runs google analytics, and cannot work when fetch requests are disabled (also suitable for sending back anything), let alone disabling scripts