Overview
If need to shut down immediately, shutdown -h now does it in one step. "now" means "immediately," and though it's quick, it still follows a safe shutdown sequence — much more reliable than pulling the plug. What's even better is that you can cancel a scheduled shutdown. If you change your mind after setting a timer, just type shutdown -c, and you can even add a message like shutdown -c "Maintenance canceled, continue using" so other users see the notification right away — especially useful in multi-user environments.The poweroff command is the "lazy person's choice" — just type it and the system shuts down and powers off without any fuss. I often use it on my personal Linux laptop, since I'm the only user, so I don't need to notify anyone. I just type the command, grab my bag, and by the time I'm ready to leave, the machine is off. However, it doesn't give any warning, so if you use it on a server, you could wipe out a colleague's unsaved work. I once helped a friend maintain a server and casually typed poweroff — he lost all his unsaved code. I still feel embarrassed about it.
The halt command is similar to poweroff, but it's "gentler" — it only stops the system but might not power off the hardware. I once used it on an old machine with a legacy Linux distribution. After typing halt, the screen went dark, but the computer's fan was still spinning, and I had to manually press the power button to turn it off. After some research, I learned that older hardware didn't support automatic power-off. On modern Linux systems, halt -p forces a power-off, similar to poweroff, but for everyday use, poweroff is more straightforward.
Newer Linux distributions (like Ubuntu 16.04 and later) support systemctl. To shut down, use systemctl poweroff; to reboot, systemctl reboot. This command is compatible across servers and personal machines, and it shows a clear shutdown process — for example, "Stopping nginx service," "Unmounting /home partition" — giving you a sense of security. I now use it for managing cloud servers, and when issues arise, I can check the logs to see which service didn't shut down cleanly.
There's also an obscure but useful command: init 0. It shuts down the system by changing the runlevel (in Linux, 0 means shutdown, 6 means reboot). I've used it when maintaining physical servers in data centers — it often works even when other commands fail. But it's "hardcore" and not recommended for beginners — if you accidentally type init 6 instead, you'll reboot instead of shutting down, which can be confusing.
A few pitfalls to avoid: first, regular users need to prefix commands with sudo, e.g., sudo shutdown -h now, or you'll get a "permission denied" error. Second, never use poweroff on a remote server — it's better to use shutdown with a grace period. Third, avoid poweroff -f unless the system is completely frozen, as it can corrupt the file system — I learned this the hard way and spent half a day recovering data.
You don't need to memorize all these commands. Just remember the scenario: for multi-user environments, use shutdown; for single-user and speed, use poweroff; for newer systems, systemctl is more standardized; and for emergencies, consider init 0. With practice, you'll find these commands are more flexible and reassuring than clicking a mouse.
