Search for a command to run...
I'm a dedicated software engineer with a passion for bringing hardware and software together to create robust and efficient solutions. I thrive on optimizing performance, managing power consumption, and ensuring the reliability of devices from concept to deployment.
🦊
No comments yet. Be the first to comment.
I have been a huge proponent of open-source software. Yet, I have always used Windows as my operating system. Times have changed and I find it even more important to switch to the Linux ecosystem.
There’s a nasty issue in VirtualBox where you won’t be able to run virtual machines on Linux distros. The error shows something similar to: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up ...
I recently got the idea to recreate the classic arcade game of Pong. Pong is a relatively simple game with little programming required to get it up and running. In this article, we will see how the co
Do you ever wake up in the morning and think, 'I should make the digital rain effect from the Matrix franchise? Well, I did, and so here we go. For those of you who don't know, the Matrix franchise ha
When you're working on Embedded firmware or low level development, it's important to have a proper logging system in place. Logging helps with debugging, tracking values and monitoring the system for
I always thought that when we compile a C code, it ‘just works’. No other fancy code runs to make our code function, like in the case for Java and Python. But turns out, it’s not exactly true. There are some work that happens behind the scenes when w...
Ever heard tech bros say, ‘switch statements are more efficient than if-else statements’? I certainly have. But have you thought of whether this is actually true? Well, is it actually true? The answer is that ‘it’s complicated!’ Let’s discuss. While ...
Do you think you know how to shut down your Linux computer? Think again! There are more ways in which you can shut down your system than the control panel. All you need is the terminal and sudo privileges. Here’s a break-down of the shutdown command in Linux.
The shutdown command in Linux (Bash) is a powerful utility used to safely halt, power off, or reboot the system. It allows administrators to schedule these actions and notify logged-in users. The general structure of this command is as below:
shutdown [OPTIONS...] [TIME] [MESSAGE]
[OPTIONS...] - Controls the specific action (halt, power off, reboot) and other behaviours.
[TIME] - Specifies when to perform the shutdown. This is often a mandatory argument if you want to specify a message or schedule the shutdown.
[MESSAGE] - An optional message to be broadcast to all logged-in users.
Under [OPTIONS...], the shutdown command allows several options for the shutdown process.
-H/--halt - Halts the machine. This stops all CPU functions but leaves the power on.
-P/--poweroff - Powers off the machine. This is often the default behaviour if neither -h (legacy option to override the previous command unless the previous command is —halt) nor -r is specified, completely cutting power.
-r/--reboot - Reboots the system.
-k - Do not actually shut down, power off, or reboot. Instead, just send the wall message to all logged-in users. This is useful for testing scripts or broadcasting warnings without performing the action.
-c - Cancels a pending shutdown. This can only be used if a time argument was specified previously to schedule a shutdown. You cannot specify a TIME or MESSAGE with this option.
--no-wall - Do not send a wall message before halting, powering off, or rebooting.
--show - Shows a pending shutdown action and time if there is any.
-t SEC - Tells init (or systemd) to wait SEC seconds between sending warning messages and the kill signal to processes. Defaults to 5 seconds.
-f - Skips the file system check (fsck) on the next reboot. Use with caution as it can lead to data inconsistencies if not used properly.
-F - Forces the file system check (fsck) on the next reboot. Useful after an unclean shutdown.
Under the [TIME] argument, you can provide a timeout for the shutdown to occur.
now - Triggers an immediate shutdown. This is an alias for +0.
+m - Specifies a shutdown in m minutes from now. For example, +10 means shutdown in 10 minutes.
hh:mm - Specifies an absolute time in 24-hour format. For example, 17:30 means shutdown at 5:30 PM.
Under [MESSAGE] argument, you can specify a message to be broadcasted to all logged-in users of the device before shutting down.
Here are a few examples with descriptions as to what they do:
sudo shutdown now
Shuts down the system immediately.
sudo shutdown -r +5 "System rebooting for maintenance. Please save your work."
Reboots the system in 5 minutes with the message ‘System rebooting for maintenance. Please save your work.’
sudo shutdown -P 23:00
Shut down the system at 11:00 PM.
sudo shutdown -c
Cancel any pending shut-downs.
sudo shutdown -k "The system will not be going down for maintenance."
Do not shut down or reboot but only display the message
‘The system will not be going down for maintenance.’
It is important to remember that the shutdown command require administrator privileges. Thus, it is important to run the shutdown command with sudo. Although not that important to remember, if a shutdown is scheduled, it sends warning messages to logged-in users, allowing them to save their work. A file /run/nologin is created (usually 5 minutes before the scheduled time) to prevent further logins.
On modern Linux distributions using systemd, shutdown often acts as a compatibility wrapper, internally invoking equivalent systemctl commands (e.g., systemctl poweroff, systemctl reboot, systemctl halt). While systemctl offers more granular control over system states, shutdown remains a convenient and widely used command, especially for scheduled actions.
While shutdown is the most common command, the following aliases are also available to simplify the specific commands:
reboot
Simply reboots the system, similar to the command shutdown -r now.
halt
Simply halts the system, similar to the command shutdown -H now.
poweroff
Simply powers off the system, similar to the command shutdown now.
Other than this, the underlying systemctl provide a lot more options should you choose to use the underlying commands:
sudo systemctl poweroff - Powers off the system immediately.
sudo systemctl reboot - Reboots the system immediately.
sudo systemctl halt - Halts the system immediately (may or may not power off, depending on system configuration).
sudo systemctl suspend: -Puts the system into a low-power state, keeping memory powered (like sleep mode).
sudo systemctl hibernate - Saves the system's state to disk and powers off, allowing a full restore upon next boot.
sudo systemctl hybrid-sleep - Attempts to suspend to RAM and disk (combines suspend and hibernate).
The systemctl commands are graceful shutdown commands, meaning that they will attempt a graceful shutdown, stopping processes and syncing file systems before the final action. Using -f or --force with any of them can bypass these graceful steps, potentially leading to data loss if not used carefully.