What is the difference between reboot and shutdown in Ubuntu/Linux?
Clash Royale CLAN TAG#URR8PPP
up vote
4
down vote
favorite
Yesterday I, from the gui, shut my computer down to physically move it. Then I turned it back on.
Today when I ssh into it from a different computer I'm told "* System restart required *"
It's reasonable to think I had a reboot left over from packages I installed last week, but that would mean a full power down isn't a superset of a reboot.
I'm using Ubuntu 16.04.4 LTS
ubuntu
asked Apr 20 at 15:28
Dark Matter
1867
add a comment |Â
up vote
4
down vote
favorite
Yesterday I, from the gui, shut my computer down to physically move it. Then I turned it back on.
Today when I ssh into it from a different computer I'm told "* System restart required *"
It's reasonable to think I had a reboot left over from packages I installed last week, but that would mean a full power down isn't a superset of a reboot.
I'm using Ubuntu 16.04.4 LTS
ubuntu
asked Apr 20 at 15:28
Dark Matter
1867
4
ubuntu uses a cron script to automatically update your packages. if any new packages has been install it will notice you to reboot
– Kiwy
Apr 20 at 15:50
I know in recent Windows versions, shutting down is often configured to do something like hibernation, while restarting will actually shut down and start again. I'm not aware of that ever happening in Linux (but I hope they don't start doing that).
– Shule
Apr 20 at 21:44
And that script runs right at boot, so it's possible the system has installed new updates before you have logged in.
– Michael Hampton
Apr 21 at 1:24
1
The question in the title is not the question being asked. For an answer to the question in the title, see unix.stackexchange.com/questions/195898 and the like. The question actually being asked is Why did powering my machine off and then on again not count as a reboot for the package installer?
– JdeBP
Apr 21 at 9:06
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
Yesterday I, from the gui, shut my computer down to physically move it. Then I turned it back on.
Today when I ssh into it from a different computer I'm told "* System restart required *"
It's reasonable to think I had a reboot left over from packages I installed last week, but that would mean a full power down isn't a superset of a reboot.
I'm using Ubuntu 16.04.4 LTS
ubuntu
asked Apr 20 at 15:28
Dark Matter
1867
Yesterday I, from the gui, shut my computer down to physically move it. Then I turned it back on.
Today when I ssh into it from a different computer I'm told "* System restart required *"
It's reasonable to think I had a reboot left over from packages I installed last week, but that would mean a full power down isn't a superset of a reboot.
I'm using Ubuntu 16.04.4 LTS
ubuntu
asked Apr 20 at 15:28
Dark Matter
1867
edited Apr 20 at 18:33
asked Apr 20 at 15:28
Dark Matter
1867
asked Apr 20 at 15:28
Dark Matter
1867
asked Apr 20 at 15:28
Dark Matter
1867
1867
4
ubuntu uses a cron script to automatically update your packages. if any new packages has been install it will notice you to reboot
– Kiwy
Apr 20 at 15:50
I know in recent Windows versions, shutting down is often configured to do something like hibernation, while restarting will actually shut down and start again. I'm not aware of that ever happening in Linux (but I hope they don't start doing that).
– Shule
Apr 20 at 21:44
And that script runs right at boot, so it's possible the system has installed new updates before you have logged in.
– Michael Hampton
Apr 21 at 1:24
1
The question in the title is not the question being asked. For an answer to the question in the title, see unix.stackexchange.com/questions/195898 and the like. The question actually being asked is Why did powering my machine off and then on again not count as a reboot for the package installer?
– JdeBP
Apr 21 at 9:06
add a comment |Â
4
ubuntu uses a cron script to automatically update your packages. if any new packages has been install it will notice you to reboot
– Kiwy
Apr 20 at 15:50
I know in recent Windows versions, shutting down is often configured to do something like hibernation, while restarting will actually shut down and start again. I'm not aware of that ever happening in Linux (but I hope they don't start doing that).
– Shule
Apr 20 at 21:44
And that script runs right at boot, so it's possible the system has installed new updates before you have logged in.
– Michael Hampton
Apr 21 at 1:24
1
The question in the title is not the question being asked. For an answer to the question in the title, see unix.stackexchange.com/questions/195898 and the like. The question actually being asked is Why did powering my machine off and then on again not count as a reboot for the package installer?
– JdeBP
Apr 21 at 9:06
4
4
ubuntu uses a cron script to automatically update your packages. if any new packages has been install it will notice you to reboot
– Kiwy
Apr 20 at 15:50
ubuntu uses a cron script to automatically update your packages. if any new packages has been install it will notice you to reboot
– Kiwy
Apr 20 at 15:50
I know in recent Windows versions, shutting down is often configured to do something like hibernation, while restarting will actually shut down and start again. I'm not aware of that ever happening in Linux (but I hope they don't start doing that).
– Shule
Apr 20 at 21:44
I know in recent Windows versions, shutting down is often configured to do something like hibernation, while restarting will actually shut down and start again. I'm not aware of that ever happening in Linux (but I hope they don't start doing that).
– Shule
Apr 20 at 21:44
And that script runs right at boot, so it's possible the system has installed new updates before you have logged in.
– Michael Hampton
Apr 21 at 1:24
And that script runs right at boot, so it's possible the system has installed new updates before you have logged in.
– Michael Hampton
Apr 21 at 1:24
1
1
The question in the title is not the question being asked. For an answer to the question in the title, see unix.stackexchange.com/questions/195898 and the like. The question actually being asked is Why did powering my machine off and then on again not count as a reboot for the package installer?
– JdeBP
Apr 21 at 9:06
The question in the title is not the question being asked. For an answer to the question in the title, see unix.stackexchange.com/questions/195898 and the like. The question actually being asked is Why did powering my machine off and then on again not count as a reboot for the package installer?
– JdeBP
Apr 21 at 9:06
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
11
down vote
accepted
At the core, there is no difference between Shutdown or Reboot, with regards to the "System Restart Required" message. Both a shutdown and a reboot will clear it. However, this only applies when you don't have a new pending update that requires a reboot to completely apply, and automatic updates could run on your system since the 'last reboot' you mentioned.
As such, you need to be mindful of whether your system has unattended-upgrades installed and enabled. If this is the case, your system gets updates once a day or so, and if you have automatic updates set up to install all available updates (not just security-only updates), then it will autorun and autoinstall updates at its configured time point. The best way to determine that is to look at /var/log/apt/history.log, where automatic updates will show up. This can explain an 'unexpected' "Restart Required" message because since the last reboot your system might have gotten new updates that triggered the message.
answered Apr 20 at 16:33
Thomas Ward
1,3182927
add a comment |Â
up vote
2
down vote
Never mind.
"tail /var/log/apt/history.log"
shows an automatic update this morning at 6am.
So I apparently have automatic updates on, and the timing was just really tight.
answered Apr 20 at 16:28
Dark Matter
1867
1
I didn't see this answer, whoops. Serves me right for trying to answer while on my phone and not my computer (oops).
– Thomas Ward
Apr 20 at 16:34
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
11
down vote
accepted
At the core, there is no difference between Shutdown or Reboot, with regards to the "System Restart Required" message. Both a shutdown and a reboot will clear it. However, this only applies when you don't have a new pending update that requires a reboot to completely apply, and automatic updates could run on your system since the 'last reboot' you mentioned.
As such, you need to be mindful of whether your system has unattended-upgrades installed and enabled. If this is the case, your system gets updates once a day or so, and if you have automatic updates set up to install all available updates (not just security-only updates), then it will autorun and autoinstall updates at its configured time point. The best way to determine that is to look at /var/log/apt/history.log, where automatic updates will show up. This can explain an 'unexpected' "Restart Required" message because since the last reboot your system might have gotten new updates that triggered the message.
answered Apr 20 at 16:33
Thomas Ward
1,3182927
add a comment |Â
up vote
11
down vote
accepted
At the core, there is no difference between Shutdown or Reboot, with regards to the "System Restart Required" message. Both a shutdown and a reboot will clear it. However, this only applies when you don't have a new pending update that requires a reboot to completely apply, and automatic updates could run on your system since the 'last reboot' you mentioned.
As such, you need to be mindful of whether your system has unattended-upgrades installed and enabled. If this is the case, your system gets updates once a day or so, and if you have automatic updates set up to install all available updates (not just security-only updates), then it will autorun and autoinstall updates at its configured time point. The best way to determine that is to look at /var/log/apt/history.log, where automatic updates will show up. This can explain an 'unexpected' "Restart Required" message because since the last reboot your system might have gotten new updates that triggered the message.
answered Apr 20 at 16:33
Thomas Ward
1,3182927
add a comment |Â
up vote
11
down vote
accepted
up vote
11
down vote
accepted
At the core, there is no difference between Shutdown or Reboot, with regards to the "System Restart Required" message. Both a shutdown and a reboot will clear it. However, this only applies when you don't have a new pending update that requires a reboot to completely apply, and automatic updates could run on your system since the 'last reboot' you mentioned.
As such, you need to be mindful of whether your system has unattended-upgrades installed and enabled. If this is the case, your system gets updates once a day or so, and if you have automatic updates set up to install all available updates (not just security-only updates), then it will autorun and autoinstall updates at its configured time point. The best way to determine that is to look at /var/log/apt/history.log, where automatic updates will show up. This can explain an 'unexpected' "Restart Required" message because since the last reboot your system might have gotten new updates that triggered the message.
answered Apr 20 at 16:33
Thomas Ward
1,3182927
At the core, there is no difference between Shutdown or Reboot, with regards to the "System Restart Required" message. Both a shutdown and a reboot will clear it. However, this only applies when you don't have a new pending update that requires a reboot to completely apply, and automatic updates could run on your system since the 'last reboot' you mentioned.
As such, you need to be mindful of whether your system has unattended-upgrades installed and enabled. If this is the case, your system gets updates once a day or so, and if you have automatic updates set up to install all available updates (not just security-only updates), then it will autorun and autoinstall updates at its configured time point. The best way to determine that is to look at /var/log/apt/history.log, where automatic updates will show up. This can explain an 'unexpected' "Restart Required" message because since the last reboot your system might have gotten new updates that triggered the message.
answered Apr 20 at 16:33
Thomas Ward
1,3182927
edited Apr 21 at 21:56
answered Apr 20 at 16:33
Thomas Ward
1,3182927
answered Apr 20 at 16:33
Thomas Ward
1,3182927
answered Apr 20 at 16:33
Thomas Ward
1,3182927
1,3182927
add a comment |Â
add a comment |Â
up vote
2
down vote
Never mind.
"tail /var/log/apt/history.log"
shows an automatic update this morning at 6am.
So I apparently have automatic updates on, and the timing was just really tight.
answered Apr 20 at 16:28
Dark Matter
1867
1
I didn't see this answer, whoops. Serves me right for trying to answer while on my phone and not my computer (oops).
– Thomas Ward
Apr 20 at 16:34
add a comment |Â
up vote
2
down vote
Never mind.
"tail /var/log/apt/history.log"
shows an automatic update this morning at 6am.
So I apparently have automatic updates on, and the timing was just really tight.
answered Apr 20 at 16:28
Dark Matter
1867
1
I didn't see this answer, whoops. Serves me right for trying to answer while on my phone and not my computer (oops).
– Thomas Ward
Apr 20 at 16:34
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Never mind.
"tail /var/log/apt/history.log"
shows an automatic update this morning at 6am.
So I apparently have automatic updates on, and the timing was just really tight.
answered Apr 20 at 16:28
Dark Matter
1867
Never mind.
"tail /var/log/apt/history.log"
shows an automatic update this morning at 6am.
So I apparently have automatic updates on, and the timing was just really tight.
answered Apr 20 at 16:28
Dark Matter
1867
answered Apr 20 at 16:28
Dark Matter
1867
answered Apr 20 at 16:28
Dark Matter
1867
answered Apr 20 at 16:28
Dark Matter
1867
1867
1
I didn't see this answer, whoops. Serves me right for trying to answer while on my phone and not my computer (oops).
– Thomas Ward
Apr 20 at 16:34
add a comment |Â
1
I didn't see this answer, whoops. Serves me right for trying to answer while on my phone and not my computer (oops).
– Thomas Ward
Apr 20 at 16:34
1
1
I didn't see this answer, whoops. Serves me right for trying to answer while on my phone and not my computer (oops).
– Thomas Ward
Apr 20 at 16:34
I didn't see this answer, whoops. Serves me right for trying to answer while on my phone and not my computer (oops).
– Thomas Ward
Apr 20 at 16:34
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438969%2fwhat-is-the-difference-between-reboot-and-shutdown-in-ubuntu-linux%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
4
ubuntu uses a cron script to automatically update your packages. if any new packages has been install it will notice you to reboot
– Kiwy
Apr 20 at 15:50
I know in recent Windows versions, shutting down is often configured to do something like hibernation, while restarting will actually shut down and start again. I'm not aware of that ever happening in Linux (but I hope they don't start doing that).
– Shule
Apr 20 at 21:44
And that script runs right at boot, so it's possible the system has installed new updates before you have logged in.
– Michael Hampton
Apr 21 at 1:24
1
The question in the title is not the question being asked. For an answer to the question in the title, see unix.stackexchange.com/questions/195898 and the like. The question actually being asked is Why did powering my machine off and then on again not count as a reboot for the package installer?
– JdeBP
Apr 21 at 9:06