{"id":3255,"date":"2023-06-30T22:41:34","date_gmt":"2023-06-30T22:41:34","guid":{"rendered":"https:\/\/www.copahost.com\/blog\/?p=3255"},"modified":"2026-09-24T22:55:59","modified_gmt":"2026-09-24T22:55:59","slug":"linux-reboot-command","status":"publish","type":"post","link":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/","title":{"rendered":"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Rebooting a Linux system might seem straightforward, but there are several ways to do it depending on your needs and the system\u2019s condition. Whether you&#8217;re a new Linux user or an experienced sysadmin, knowing multiple Linux reboot commands can be useful, especially in troubleshooting or maintenance situations. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From standard commands to emergency alternatives, Linux offers flexible options that can ensure a smooth restart or provide a quick fix when your system becomes unresponsive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this post, we\u2019ll walk you through eight easy methods to reboot a Linux system. We\u2019ll cover everything from the most common commands, like <strong><code>reboot<\/code> <\/strong>and <code><strong>shutdown<\/strong><\/code>, to more advanced techniques like using <strong><code>systemctl<\/code> <\/strong>and <code><strong>init<\/strong><\/code>. Each method has its advantages and specific use cases, so by the end, you\u2019ll know exactly which command to use in various scenarios to keep your system running smoothly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-center counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_1_%E2%80%93_The_standard_Linux_Reboot_Command\" >Method 1 &#8211; The standard Linux Reboot Command<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_2_%E2%80%93_sudo_shutdown_-r_now\" >Method 2 &#8211; sudo shutdown -r now<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Reboot_vs_shutdown_vs_halt_vs_poweroff\" >Reboot vs shutdown vs halt vs poweroff<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Reboot_command_by_distribution\" >Reboot command by distribution<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_3_%E2%80%93_Linux_reboot_command_using_systemctl\" >Method 3 &#8211; Linux reboot command using systemctl<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_4_%E2%80%93_reboot_Linux_using_init\" >Method 4 &#8211; reboot Linux using init<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_5_%E2%80%93_Linux_reboot_using_telinit\" >Method 5 &#8211; Linux reboot using telinit<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_6_%E2%80%93_Using_sysrq-trigger\" >Method 6 &#8211; Using sysrq-trigger<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_7_%E2%80%93_Reboot_a_remote_Linux_server_over_SSH\" >Method 7 \u2013 Reboot a remote Linux server over SSH<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Method_8_%E2%80%93_Forceful_Linux_reboot_command\" >Method 8 &#8211; Forceful Linux reboot command<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Best_practices\" >Best practices<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Frequently_asked_questions\" >Frequently asked questions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_1_%E2%80%93_The_standard_Linux_Reboot_Command\"><\/span>Method 1 &#8211; The standard Linux Reboot Command<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The reboot command is used in Linux systems to initiate a system reboot. It is a common way to restart the operating system. It&#8217;s worth noting that the reboot command requires root or superuser privileges, so you may need to add the sudo prefix to it and enter your password to execute it successfully.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The basic syntax of the <code>reboot<\/code> command is as follows:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo reboot<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This will give a message like the image shown below:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"725\" src=\"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-command-1024x725.png\" alt=\"Linux reboot command\" class=\"wp-image-3256\" srcset=\"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-command-1024x725.png 1024w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-command-300x212.png 300w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-command-768x544.png 768w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-command.png 1364w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Options<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">This command has various options that you can use to specify the behavior of the reboot. Here are some commonly used options:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>--help<\/code> : This option displays the help information for the <code>reboot<\/code> command by showing available options and their usage. Here is the information it gives:<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"725\" src=\"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-help-1024x725.png\" alt=\"Linux reboot command help option\" class=\"wp-image-3257\" srcset=\"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-help-1024x725.png 1024w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-help-300x212.png 300w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-help-768x544.png 768w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/reboot-help.png 1364w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">As you see in the image, other options are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>--halt<\/code>: halts the system instead of rebooting it. The machine stops, and on some hardware stays powered on.<\/li>\n\n\n\n<li><code>-f<\/code> or <code>--force<\/code>: This option forces an immediate reboot, performing a hard shutdown.<\/li>\n\n\n\n<li><code>-p<\/code> or <code>--poweroff<\/code>: This option shuts down the system and switches it off completely instead of rebooting.<\/li>\n\n\n\n<li><code>-w<\/code> or <code>--wtmp-only<\/code>: This option does not actually perform the reboot. It writes records to the <code>\/var\/log\/wtmp<\/code> file.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_2_%E2%80%93_sudo_shutdown_-r_now\"><\/span>Method 2 &#8211; sudo shutdown -r now<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>shutdown<\/code> command is used to shut down a Linux system. It provides a controlled shutdown process as it allows setting the shutdown time, display warning messages or cancel the shutdown. The point is the <code>shutdown -r now<\/code> command and the <code>reboot<\/code> command both serve the purpose of restarting a Linux system.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo shutdown -r now<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>-r<\/code> option specifies that the system will be rebooted, while the <code>now<\/code> option specifies the operation will be performed immediately. This is why two of these commands are alternatives to each other. Here is an example:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"725\" src=\"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now-1024x725.png\" alt=\"shutdown -r now\" class=\"wp-image-3258\" srcset=\"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now-1024x725.png 1024w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now-300x212.png 300w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now-768x544.png 768w, https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now.png 1364w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The shutdown command also accepts different options and parameters, for example, the command scheduling a shutdown at 10:40 PM (22:40):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo shutdown -r 22:40<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Note that, these were a few examples to give insights to the shutdown command. It has various options to change the behaviour of the shutdown process.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Reboot_vs_shutdown_vs_halt_vs_poweroff\"><\/span>Reboot vs shutdown vs halt vs poweroff<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These commands look alike and do different things \u2014 and on a remote server, the difference between rebooting and powering off is the difference between waiting a minute and opening a support ticket.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Command<\/th><th>What it does<\/th><\/tr><\/thead><tbody><tr><td><code>sudo reboot<\/code><\/td><td>Restarts the system<\/td><\/tr><tr><td><code>sudo shutdown -r now<\/code><\/td><td>Restarts immediately \u2014 same result as <code>reboot<\/code><\/td><\/tr><tr><td><code>sudo shutdown now<\/code><\/td><td><strong>Powers off.<\/strong> It does not reboot<\/td><\/tr><tr><td><code>sudo poweroff<\/code> or <code>sudo shutdown -h now<\/code><\/td><td>Powers off<\/td><\/tr><tr><td><code>sudo halt<\/code><\/td><td>Stops the system; on some hardware it doesn&#8217;t cut the power<\/td><\/tr><tr><td><code>sudo shutdown -r +10<\/code><\/td><td>Reboots in 10 minutes, warning logged-in users<\/td><\/tr><tr><td><code>sudo shutdown -c<\/code><\/td><td>Cancels a scheduled shutdown or reboot<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>About &#8220;reboot now&#8221;:<\/strong> the <code>now<\/code> is harmless but unnecessary \u2014 <code>reboot<\/code> has no delay to skip. <code>now<\/code> belongs to <code>shutdown<\/code>: without a time, <code>shutdown<\/code> waits one minute on systemd systems.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Reboot_command_by_distribution\"><\/span>Reboot command by distribution<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Distribution<\/th><th>Reboot command<\/th><th>Notes<\/th><\/tr><\/thead><tbody><tr><td>Ubuntu, Debian, Linux Mint<\/td><td><code>sudo reboot<\/code> or <code>sudo systemctl reboot<\/code><\/td><td>systemd<\/td><\/tr><tr><td>RHEL, CentOS, Rocky Linux, AlmaLinux, Fedora<\/td><td><code>sudo reboot<\/code> or <code>sudo systemctl reboot<\/code><\/td><td>systemd; <code>init 6<\/code> still works<\/td><\/tr><tr><td>Arch Linux<\/td><td><code>sudo reboot<\/code><\/td><td>systemd<\/td><\/tr><tr><td>Alpine Linux<\/td><td><code>reboot<\/code> (as root)<\/td><td>Uses OpenRC, not systemd \u2014 <code>systemctl<\/code> isn&#8217;t available<\/td><\/tr><tr><td>Raspberry Pi OS<\/td><td><code>sudo reboot<\/code><\/td><td>Debian-based<\/td><\/tr><tr><td>WSL on Windows<\/td><td><code>wsl --shutdown<\/code> in PowerShell, then reopen<\/td><td>Linux reboot commands don&#8217;t restart WSL itself<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_3_%E2%80%93_Linux_reboot_command_using_systemctl\"><\/span>Method 3 &#8211; Linux reboot command using systemctl<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On modern Linux distributions that use systemd (most do today, like Ubuntu, Debian, CentOS, and Fedora), <strong><code>systemctl<\/code> <\/strong>is the standard way to manage the system \u2014 including restarting it. This is the most &#8220;correct&#8221; method on current systems, as it lets systemd shut down services cleanly before rebooting.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl reboot<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">It does the same job as the <code>reboot<\/code> command, which on systemd-based systems is actually just a shortcut to this. Use it when you want the canonical, modern approach.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_4_%E2%80%93_reboot_Linux_using_init\"><\/span>Method 4 &#8211; reboot Linux using init<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <strong><code>init<\/code> <\/strong>command changes the system&#8217;s <strong>runlevel<\/strong> \u2014 a number that defines the system&#8217;s operating state. Runlevel 6 is reserved for rebooting, so <code><strong>init 6<\/strong><\/code> triggers a restart.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo init 6<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This is the traditional method from older, SysV-init systems. On modern systemd distributions it still works (it&#8217;s mapped to the systemd reboot target for compatibility), but <code><strong>systemctl reboot<\/strong><\/code> is preferred. Use<strong> <code>init 6<\/code><\/strong> mainly on older systems or out of habit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_5_%E2%80%93_Linux_reboot_using_telinit\"><\/span>Method 5 &#8211; Linux reboot using telinit<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><code>telinit<\/code> <\/strong>is closely related to <strong><code>init<\/code> <\/strong>\u2014 it tells the init process to switch to a given runlevel. Like <code><strong>init 6<\/strong><\/code>, using runlevel 6 triggers a reboot.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo telinit 6<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The practical difference is subtle: <strong><code>telinit<\/code> <\/strong>signals the already-running init process to change state, which is technically the more correct way to request a runlevel change. In everyday use, <strong><code>init 6<\/code> <\/strong>and <code><strong>telinit 6<\/strong><\/code> produce the same result on most systems.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_6_%E2%80%93_Using_sysrq-trigger\"><\/span>Method 6 &#8211; Using sysrq-trigger<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is a low-level <strong>hard reboot<\/strong>. It uses the kernel&#8217;s &#8220;magic SysRq&#8221; feature to restart the machine immediately, bypassing the normal shutdown sequence \u2014 it does <strong>not<\/strong> unmount filesystems cleanly or stop services gracefully.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>echo b | sudo tee \/proc\/sysrq-trigger<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A safer sequence, if the system still accepts commands:<\/strong> flush and protect the disks before the reboot.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>echo s | sudo tee \/proc\/sysrq-trigger<br>echo u | sudo tee \/proc\/sysrq-trigger<br>echo b | sudo tee \/proc\/sysrq-trigger<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>s<\/code> writes pending data to disk, <code>u<\/code> remounts filesystems read-only, and only then <code>b<\/code> reboots \u2014 the same idea as the classic REISUB sequence on a frozen keyboard.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Because it skips the clean shutdown, it carries a real risk of data loss or filesystem corruption. Reserve it for emergencies \u2014 for example, when the system is frozen and no standard command responds, as a last resort before pulling the power.<\/p>\n\n\n\n<link rel=\"stylesheet\" href=\"https:\/\/cdn.jsdelivr.net\/npm\/@tabler\/icons-webfont@latest\/tabler-icons.min.css\">\n\n<style>\n  .warn-box {\n    display: flex;\n    gap: 14px;\n    align-items: flex-start;\n    background: #FCEBEB;\n    border: 1px solid #E0A0A0;\n    border-left: 4px solid #A32D2D;\n    border-radius: 12px;\n    padding: 16px 18px;\n    margin: 1rem 0;\n  }\n  .warn-icon {\n    width: 34px; height: 34px;\n    background: #F5C6C6;\n    border-radius: 8px;\n    display: flex; align-items: center; justify-content: center;\n    flex-shrink: 0;\n  }\n  .warn-icon i { font-size: 19px; color: #791F1F; }\n  .warn-content { display: flex; flex-direction: column; gap: 4px; }\n  .warn-label { font-weight: 600; color: #791F1F; }\n  .warn-text { color: #A32D2D; line-height: 1.6; }\n  .warn-text strong { color: #791F1F; }\n<\/style>\n\n<div class=\"warn-box\">\n  <div class=\"warn-icon\">\n    <i class=\"ti ti-alert-triangle\"><\/i>\n  <\/div>\n  <div class=\"warn-content\">\n    <span class=\"warn-label\">Warning: risk of data loss<\/span>\n    <span class=\"warn-text\">\n      The methods below are <strong>hard reboots<\/strong>. They restart the system immediately, without stopping services or unmounting filesystems cleanly \u2014 which can cause <strong>data loss or filesystem corruption<\/strong>. Use them only in emergencies, when standard reboot commands no longer respond, and save your work first whenever possible.\n    <\/span>\n  <\/div>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_7_%E2%80%93_Reboot_a_remote_Linux_server_over_SSH\"><\/span>Method 7 \u2013 Reboot a remote Linux server over SSH<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On a server you reach over SSH, the reboot is one line:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh -t user@your-server 'sudo systemctl reboot'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>-t<\/code> lets <code>sudo<\/code> ask for your password. Your session drops as soon as the server starts shutting down \u2014 that&#8217;s expected. Wait a minute, then check it&#8217;s back:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ping your-server<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Once it answers, reconnect and confirm the reboot actually happened:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>uptime -s<br>who -b<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Both show when the system last booted.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#x26a0;&#xfe0f; <strong>Before rebooting a production server, confirm your services start on boot<\/strong> \u2014 <code>systemctl is-enabled nginx<\/code>, for example. Otherwise the server comes back and the site doesn&#8217;t. And if it doesn&#8217;t come back at all, use your provider&#8217;s console or the power-cycle option in the control panel.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Method_8_%E2%80%93_Forceful_Linux_reboot_command\"><\/span>Method 8 &#8211; Forceful Linux reboot command<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>-f<\/code> (force) option tells <code>reboot<\/code> to restart the machine immediately, skipping the usual shutdown scripts and not stopping services gracefully<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo reboot -f<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On systemd, <code>reboot -f<\/code> still kills processes and unmounts or remounts filesystems read-only before restarting \u2014 it only skips stopping services properly. Doubling it, <code>reboot -ff<\/code>, skips even that and restarts instantly, like the SysRq method.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Like the SysRq method, this is not a clean reboot and can risk data loss, so it&#8217;s not for routine use. It&#8217;s helpful when a normal <strong><code>reboot<\/code> <\/strong>hangs or doesn&#8217;t respond, but the system is still partially functional. As a rule: try the clean methods first, and only force a reboot when they fail.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Best_practices\"><\/span>Best practices<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When rebooting a Linux system, there are several considerations to keep in mind to ensure a successful restart. Here are some important points to consider:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Save your work<\/strong>: Save any unsaved work and close any open applications or documents to avoid data loss or corruption.<\/li>\n\n\n\n<li><strong>Check whether a reboot is actually needed.<\/strong> On Ubuntu and Debian, the file <code>\/var\/run\/reboot-required<\/code> exists when an update needs a restart. On RHEL-based systems, <code>sudo dnf needs-restarting -r<\/code> tells you.<\/li>\n\n\n\n<li><strong>Warn logged-in users<\/strong> on a shared server: <code>sudo shutdown -r +5 \"Rebooting for updates\"<\/code> gives them five minutes and a message.<\/li>\n\n\n\n<li><strong>Backup important data<\/strong>: If you have important data on the system, it&#8217;s always a good idea to have a <a href=\"https:\/\/www.copahost.com\/blog\/6-tips-for-a-perfect-backup-in-your-cpanel-server\/\">backup<\/a> before rebooting.<\/li>\n\n\n\n<li><strong>Check System After Rebooting<\/strong>: Rebooting may stop some services, make sure all system processes are still running after restart.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">By following these practises, you can minimize the risk of data loss and have a successful reboot of your Linux system.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Frequently_asked_questions\"><\/span>Frequently asked questions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How do I reboot Linux from the command line?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The simplest way is to run <code>sudo reboot<\/code>. On modern systemd-based distributions, <code>sudo systemctl reboot<\/code> does the same thing and is the recommended method, as it shuts down services cleanly before restarting.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What is the reboot command in Ubuntu?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same as on any modern Linux: <code>sudo reboot<\/code>, or <code>sudo systemctl reboot<\/code>. Ubuntu, Debian and Linux Mint all use systemd, so both commands restart the system cleanly. <code>sudo shutdown -r now<\/code> works too, and lets you schedule the restart instead.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What is the difference between reboot and shutdown -r?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Both restart the system. <code>reboot<\/code> is the quick, direct command, while <code>shutdown -r<\/code> gives you more control \u2014 you can schedule the restart for a specific time and display a warning message to logged-in users. Use <code>shutdown -r now<\/code> for an immediate restart.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Does &#8220;shutdown now&#8221; reboot Linux?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">No \u2014 it powers the system off. To restart, use <code>sudo shutdown -r now<\/code> or simply <code>sudo reboot<\/code>. It&#8217;s an easy mistake to make on a remote server, where powering off means you can&#8217;t reconnect until someone turns the machine back on.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Does the reboot command require sudo?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Rebooting requires root or superuser privileges, so you normally need to prefix the command with <code>sudo<\/code> and enter your password \u2014 unless you&#8217;re already logged in as the root user.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How do I schedule a reboot in Linux?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use the <code>shutdown<\/code> command with a time. <code>sudo shutdown -r 22:40<\/code> schedules a reboot for 10:40 PM, and <code>sudo shutdown -r +10<\/code> reboots in ten minutes, warning logged-in users. To cancel a scheduled reboot, run <code>sudo shutdown -c<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How do I force a reboot when Linux is frozen?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Try <code>sudo reboot -f<\/code> first \u2014 on systemd it skips the orderly service shutdown but still unmounts filesystems. If that hangs, <code>sudo reboot -ff<\/code> restarts instantly. As a last resort, the SysRq sequence <code>s<\/code>, <code>u<\/code>, <code>b<\/code> written to <code>\/proc\/sysrq-trigger<\/code> syncs the disks, remounts them read-only and reboots. The stronger the method, the higher the risk of data loss.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What does &#8220;Call to Reboot failed: Connection timed out&#8221; mean?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That <code>systemctl<\/code> couldn&#8217;t reach the system manager in time \u2014 usually because systemd or D-Bus is overloaded or hung. Try <code>sudo systemctl reboot --force<\/code>, which skips the orderly service shutdown. If that also hangs, <code>sudo reboot -ff<\/code> or the SysRq method restarts the machine without asking systemd at all.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How do I reboot a remote Linux server over SSH?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run <code>ssh -t user@your-server 'sudo systemctl reboot'<\/code> \u2014 the <code>-t<\/code> lets <code>sudo<\/code> ask for your password. Your SSH session will disconnect as the server restarts; wait until it answers <code>ping<\/code> again, then reconnect and confirm with <code>uptime -s<\/code>. Before rebooting a production server, make sure its services are enabled to start on boot.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How do I check when Linux was last rebooted?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run <code>uptime -s<\/code> for the exact boot time, or <code>who -b<\/code> for the same information in a different format. <code>last reboot<\/code> lists the history of previous reboots, as far back as the system&#8217;s login records go.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How do I restart WSL?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Linux reboot commands don&#8217;t restart WSL itself. Close your Linux terminals and run <code>wsl --shutdown<\/code> in Windows PowerShell or Command Prompt; the next time you open a WSL terminal, it starts fresh.<\/p>\n\n\n\n<script type=\"application\/ld+json\">\n{\n\"@context\": \"https:\/\/schema.org\",\n\"@type\": \"FAQPage\",\n\"mainEntity\": [\n{\"@type\":\"Question\",\"name\":\"How do I reboot Linux from the command line?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The simplest way is to run sudo reboot. On modern systemd-based distributions, sudo systemctl reboot does the same thing and is the recommended method, as it shuts down services cleanly before restarting.\"}},\n{\"@type\":\"Question\",\"name\":\"What is the reboot command in Ubuntu?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The same as on any modern Linux: sudo reboot, or sudo systemctl reboot. Ubuntu, Debian and Linux Mint all use systemd, so both commands restart the system cleanly. shutdown -r now works too, and lets you schedule the restart instead.\"}},\n{\"@type\":\"Question\",\"name\":\"What is the difference between reboot and shutdown -r?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Both restart the system. reboot is the quick, direct command, while shutdown -r gives you more control: you can schedule the restart for a specific time and display a warning message to logged-in users. Use shutdown -r now for an immediate restart.\"}},\n{\"@type\":\"Question\",\"name\":\"Does shutdown now reboot Linux?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No, it powers the system off. To restart, use shutdown -r now or simply reboot, with sudo. It is an easy mistake to make on a remote server, where powering off means you cannot reconnect until someone turns the machine back on.\"}},\n{\"@type\":\"Question\",\"name\":\"Does the reboot command require sudo?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Yes. Rebooting requires root or superuser privileges, so you normally need to prefix the command with sudo and enter your password, unless you are already logged in as the root user.\"}},\n{\"@type\":\"Question\",\"name\":\"How do I schedule a reboot in Linux?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use the shutdown command with a time. shutdown -r 22:40 schedules a reboot for 10:40 PM, and shutdown -r +10 reboots in ten minutes, warning logged-in users. To cancel a scheduled reboot, run shutdown -c.\"}},\n{\"@type\":\"Question\",\"name\":\"How do I force a reboot when Linux is frozen?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Try reboot -f first: on systemd it skips the orderly service shutdown but still unmounts filesystems. If that hangs, reboot -ff restarts instantly. As a last resort, the SysRq sequence s, u, b written to \/proc\/sysrq-trigger syncs the disks, remounts them read-only and reboots. The stronger the method, the higher the risk of data loss.\"}},\n{\"@type\":\"Question\",\"name\":\"What does Call to Reboot failed: Connection timed out mean?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"That systemctl could not reach the system manager in time, usually because systemd or D-Bus is overloaded or hung. Try systemctl reboot with the --force option, which skips the orderly service shutdown. If that also hangs, reboot -ff or the SysRq method restarts the machine without asking systemd at all.\"}},\n{\"@type\":\"Question\",\"name\":\"How do I reboot a remote Linux server over SSH?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Run the reboot through ssh with the -t option, so sudo can ask for your password. Your SSH session will disconnect as the server restarts; wait until it answers ping again, then reconnect and confirm with uptime -s. Before rebooting a production server, make sure its services are enabled to start on boot.\"}},\n{\"@type\":\"Question\",\"name\":\"How do I check when Linux was last rebooted?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Run uptime -s for the exact boot time, or who -b for the same information in a different format. The last reboot command lists the history of previous reboots, as far back as the system's login records go.\"}},\n{\"@type\":\"Question\",\"name\":\"How do I restart WSL?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Linux reboot commands do not restart WSL itself. Close your Linux terminals and run wsl --shutdown in Windows PowerShell or Command Prompt; the next time you open a WSL terminal, it starts fresh.\"}}\n]\n}\n<\/script>\n\n\n\n<link rel=\"stylesheet\" href=\"https:\/\/cdn.jsdelivr.net\/npm\/@tabler\/icons-webfont@latest\/tabler-icons.min.css\">\n\n<style>\n  .cta-box {\n    margin: 1.5rem 0;\n    background: linear-gradient(135deg, #0C447C 0%, #185FA5 100%);\n    border-radius: 16px;\n    padding: 28px;\n    display: flex;\n    align-items: center;\n    gap: 22px;\n    flex-wrap: wrap;\n  }\n  .cta-icon {\n    width: 56px; height: 56px;\n    background: rgba(255,255,255,0.14);\n    border-radius: 12px;\n    display: flex; align-items: center; justify-content: center;\n    flex-shrink: 0;\n  }\n  .cta-icon i { font-size: 28px; color: #fff; }\n  .cta-content { flex: 1; min-width: 220px; display: flex; flex-direction: column; gap: 6px; }\n  .cta-title { font-weight: 600; color: #fff; line-height: 1.3; font-size: 1.15rem; }\n  .cta-text { color: #C5DDF4; line-height: 1.55; }\n  .cta-perks { display: flex; flex-wrap: wrap; gap: 8px; margin-top: 6px; }\n  .cta-perk {\n    display: inline-flex; align-items: center; gap: 5px;\n    background: rgba(255,255,255,0.12);\n    color: #E6F1FB;\n    border-radius: 99px;\n    padding: 3px 10px;\n    font-size: .85rem;\n  }\n  .cta-perk i { font-size: 13px; }\n  .cta-btn {\n    display: inline-flex; align-items: center; gap: 8px;\n    background: #fff;\n    color: #0C447C !important;\n    border-radius: 8px;\n    padding: 13px 22px;\n    font-weight: 600;\n    text-decoration: none !important;\n    white-space: nowrap;\n    flex-shrink: 0;\n  }\n  .cta-btn:hover { background: #E6F1FB; }\n  .cta-btn i { font-size: 17px; }\n<\/style>\n\n<div class=\"cta-box\">\n  <div class=\"cta-icon\"><i class=\"ti ti-server-bolt\"><\/i><\/div>\n  <div class=\"cta-content\">\n    <span class=\"cta-title\">Need a Linux server you fully control?<\/span>\n    <span class=\"cta-text\">Reboot, configure, and manage your own environment with root access from the command line. Copahost&#8217;s Cloud and VPS plans run on Linux with full SSH access, NVMe storage, and our own data center.<\/span>\n    <div class=\"cta-perks\">\n      <span class=\"cta-perk\"><i class=\"ti ti-key\"><\/i> Full root access<\/span>\n      <span class=\"cta-perk\"><i class=\"ti ti-brand-tabler\"><\/i> Linux distros<\/span>\n      <span class=\"cta-perk\"><i class=\"ti ti-bolt\"><\/i> NVMe storage<\/span>\n    <\/div>\n  <\/div>\n  <a class=\"cta-btn\" href=\"https:\/\/www.copahost.com\/en\/vps-hosting\" target=\"_blank\">\n    <i class=\"ti ti-arrow-right\"><\/i> View VPS &#038; Cloud plans\n  <\/a>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For almost every situation, <code>sudo reboot<\/code> or <code>sudo systemctl reboot<\/code> is all you need \u2014 they shut services down cleanly and restart the system. Use <code>shutdown -r<\/code> when you want to schedule the restart or warn other users, and remember that <code>shutdown now<\/code> on its own powers the machine off.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The forceful methods \u2014 <code>reboot -f<\/code>, <code>reboot -ff<\/code> and SysRq \u2014 are for when the clean ones stop responding, and each step down that list trades safety for certainty. On a remote server, the reboot is the easy part: confirming the services came back with it is what actually matters.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Rebooting a Linux system might seem straightforward, but there are several ways to do it depending on your needs and the system\u2019s condition. Whether you&#8217;re a new Linux user or an experienced sysadmin, knowing multiple Linux reboot commands can be useful, especially in troubleshooting or maintenance situations. From standard commands to emergency alternatives, Linux offers [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3258,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[31],"tags":[],"class_list":["post-3255","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-tutorials"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Linux Reboot Command: 8 Ways to Restart Linux from the Terminal - Copahost<\/title>\n<meta name=\"description\" content=\"Eight ways to reboot Linux from the terminal \u2014 reboot, shutdown, systemctl, init, over SSH and forced \u2014 plus the command that powers off instead.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal - Copahost\" \/>\n<meta property=\"og:description\" content=\"Eight ways to reboot Linux from the terminal \u2014 reboot, shutdown, systemctl, init, over SSH and forced \u2014 plus the command that powers off instead.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/\" \/>\n<meta property=\"og:site_name\" content=\"Copahost\" \/>\n<meta property=\"article:published_time\" content=\"2023-06-30T22:41:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-24T22:55:59+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1364\" \/>\n\t<meta property=\"og:image:height\" content=\"966\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Gustavo Gallas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Gustavo Gallas\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/\"},\"author\":{\"name\":\"Gustavo Gallas\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#\\\/schema\\\/person\\\/386b3f1f79299d43f4ceb33d26428246\"},\"headline\":\"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal\",\"datePublished\":\"2023-06-30T22:41:34+00:00\",\"dateModified\":\"2026-09-24T22:55:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/\"},\"wordCount\":2004,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/shutdown-r-now.png\",\"articleSection\":[\"Linux tutorials\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/\",\"url\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/\",\"name\":\"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal - Copahost\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/shutdown-r-now.png\",\"datePublished\":\"2023-06-30T22:41:34+00:00\",\"dateModified\":\"2026-09-24T22:55:59+00:00\",\"description\":\"Eight ways to reboot Linux from the terminal \u2014 reboot, shutdown, systemctl, init, over SSH and forced \u2014 plus the command that powers off instead.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/shutdown-r-now.png\",\"contentUrl\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/shutdown-r-now.png\",\"width\":1364,\"height\":966},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/linux-reboot-command\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/\",\"name\":\"Copahost\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#organization\",\"name\":\"Copahost\",\"url\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/03\\\/copahostlogo.png\",\"contentUrl\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/03\\\/copahostlogo.png\",\"width\":223,\"height\":40,\"caption\":\"Copahost\"},\"image\":{\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/#\\\/schema\\\/person\\\/386b3f1f79299d43f4ceb33d26428246\",\"name\":\"Gustavo Gallas\",\"description\":\"Graduated in Computing at PUC-Rio, Brazil. Specialized in IT, networking, systems administration and human and organizational development\u200b. Also have brewing skills.\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/gustavo-gallas-107926196\\\/\"],\"url\":\"https:\\\/\\\/www.copahost.com\\\/blog\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal - Copahost","description":"Eight ways to reboot Linux from the terminal \u2014 reboot, shutdown, systemctl, init, over SSH and forced \u2014 plus the command that powers off instead.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/","og_locale":"en_US","og_type":"article","og_title":"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal - Copahost","og_description":"Eight ways to reboot Linux from the terminal \u2014 reboot, shutdown, systemctl, init, over SSH and forced \u2014 plus the command that powers off instead.","og_url":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/","og_site_name":"Copahost","article_published_time":"2023-06-30T22:41:34+00:00","article_modified_time":"2026-09-24T22:55:59+00:00","og_image":[{"width":1364,"height":966,"url":"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now.png","type":"image\/png"}],"author":"Gustavo Gallas","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Gustavo Gallas","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#article","isPartOf":{"@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/"},"author":{"name":"Gustavo Gallas","@id":"https:\/\/www.copahost.com\/blog\/#\/schema\/person\/386b3f1f79299d43f4ceb33d26428246"},"headline":"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal","datePublished":"2023-06-30T22:41:34+00:00","dateModified":"2026-09-24T22:55:59+00:00","mainEntityOfPage":{"@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/"},"wordCount":2004,"commentCount":0,"publisher":{"@id":"https:\/\/www.copahost.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#primaryimage"},"thumbnailUrl":"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now.png","articleSection":["Linux tutorials"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/","url":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/","name":"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal - Copahost","isPartOf":{"@id":"https:\/\/www.copahost.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#primaryimage"},"image":{"@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#primaryimage"},"thumbnailUrl":"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now.png","datePublished":"2023-06-30T22:41:34+00:00","dateModified":"2026-09-24T22:55:59+00:00","description":"Eight ways to reboot Linux from the terminal \u2014 reboot, shutdown, systemctl, init, over SSH and forced \u2014 plus the command that powers off instead.","breadcrumb":{"@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.copahost.com\/blog\/linux-reboot-command\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#primaryimage","url":"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now.png","contentUrl":"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2023\/06\/shutdown-r-now.png","width":1364,"height":966},{"@type":"BreadcrumbList","@id":"https:\/\/www.copahost.com\/blog\/linux-reboot-command\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.copahost.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Linux Reboot Command: 8 Ways to Restart Linux from the Terminal"}]},{"@type":"WebSite","@id":"https:\/\/www.copahost.com\/blog\/#website","url":"https:\/\/www.copahost.com\/blog\/","name":"Copahost","description":"","publisher":{"@id":"https:\/\/www.copahost.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.copahost.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.copahost.com\/blog\/#organization","name":"Copahost","url":"https:\/\/www.copahost.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.copahost.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2016\/03\/copahostlogo.png","contentUrl":"https:\/\/www.copahost.com\/blog\/wp-content\/uploads\/2016\/03\/copahostlogo.png","width":223,"height":40,"caption":"Copahost"},"image":{"@id":"https:\/\/www.copahost.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.copahost.com\/blog\/#\/schema\/person\/386b3f1f79299d43f4ceb33d26428246","name":"Gustavo Gallas","description":"Graduated in Computing at PUC-Rio, Brazil. Specialized in IT, networking, systems administration and human and organizational development\u200b. Also have brewing skills.","sameAs":["https:\/\/www.linkedin.com\/in\/gustavo-gallas-107926196\/"],"url":"https:\/\/www.copahost.com\/blog\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/posts\/3255","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/comments?post=3255"}],"version-history":[{"count":19,"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/posts\/3255\/revisions"}],"predecessor-version":[{"id":6473,"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/posts\/3255\/revisions\/6473"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/media\/3258"}],"wp:attachment":[{"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/media?parent=3255"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/categories?post=3255"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.copahost.com\/blog\/wp-json\/wp\/v2\/tags?post=3255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}