And hence under no circumstances one should ship a code that just doesn’t do what it’s supposed to do in the first place, we know the cloud doesn’t use it much, but c’mon it’s a critical part of the system.
That still does stuff like unmounting filesystems (which can take a minute with snap, if they haven't fixed it), you can go further with the (rather unsafe) SysRq key "o", which tells the kernel to shut down without any preparation.
And hence under no circumstances one should ship a code that just doesn’t do what it’s supposed to do in the first place, we know the cloud doesn’t use it much, but c’mon it’s a critical part of the system.
D'oh sudo shutdown
Linux: I give a damn about you're super critical nuclear reactor loading up, this computer is going down NOW
Systemd: “A stop job is running for User Manager for UID 1000 (1s / 2min)”
Ctrl-Alt SysRQ, Pause, o (off) for that.
Well it is still shutting down
It would actually be sudo shutdown -h now. Otherwise it waits a few minutes for the control rods to drop before it shuts off the coolant control.
That still does stuff like unmounting filesystems (which can take a minute with snap, if they haven't fixed it), you can go further with the (rather unsafe) SysRq key "o", which tells the kernel to shut down without any preparation.
That's quite interesting, considering that -h flag is usually related to showing help.