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.

  • fortified_banana@beehaw.orgEnglish
    47·
    4 months ago

    I always try to consult the man pages for these kind of questions (you can search by typing ‘/’ in the man page). Here’s what the systemctl manual has to say in the specifications for the --force option:

    Note that when --force is specified twice the selected operation is executed by systemctl itself, and the system manager is not contacted. This means the command should succeed even when the system manager has crashed.

    • Epzillon@lemmy.mlOP
      151·
      4 months ago

      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!

        • ReversalHatchery@beehaw.orgEnglish
          3·
          4 months ago

          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

      • secret300@lemmy.sdf.org
        3·
        4 months ago

        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

      • desentizised@lemm.ee
        3·
        4 months ago

        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 reboot can’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.

      • 𝘋𝘪𝘳𝘬@lemmy.ml
        231·
        4 months ago

        You just really force it.

        It’s like with -v in various applications. -v means “verbose”, and -vv means “really verbose”, and -vvv means “an ungodly amount of data printed to the terminal, so much that it might crash”.

        • kungen@feddit.nu
          4·
          4 months ago

          But that’s all part of the same argument. If it was -f or -ff that’d make sense. Duplicate parameters are usually ignored in like all other programs I can think of.

          • 𝘋𝘪𝘳𝘬@lemmy.ml
            8·
            4 months ago

            The -vvv I know is the same as -v -v -v. Can’t check right now, but is the short parameter -f? So maybe give -ff a try …

          • huginn@feddit.it
            5·
            4 months ago

            It’s a dangerous command - I’d rather not run it by accidentally hitting the f key a second time.

          • teawrecks@sopuli.xyz
            3·
            4 months ago

            I agree. Specifying the same param twice like this feels like it should be idempotent. Sometimes a final cmdline string is built by multiple tools concatenating their outputs together; if each one adds --force without any way to know if it’s already been added elsewhere, this could lead to undesirable behavior.

            Even --forceforce would be better.