Why do I need to restart OS after some package upgrade? [duplicate]
Clash Royale CLAN TAG#URR8PPP
up vote
-2
down vote
favorite
This question already has an answer here:
What forces a reboot?
2 answers
On Ubuntu, when running sudo apt update; sudo apt upgrade
, why sometimes it asks me to restart my OS and sometimes not?
What do the packages that have that restart requirement have in common? Is it not possible to update such a package without restart OS requirement?
If I am correct, sudo apt update; sudo apt upgrade
can also update/upgrade kernel. Does kernel update/upgrade also require OS restart?
Thanks.
I often keep my Ubuntu up indefinitely long, because I am always running some programs and I don't want to interrupt them.
debian ubuntu apt package-management
marked as duplicate by muru, Jeff Schaller, Stephen Kitt
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
18 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
-2
down vote
favorite
This question already has an answer here:
What forces a reboot?
2 answers
On Ubuntu, when running sudo apt update; sudo apt upgrade
, why sometimes it asks me to restart my OS and sometimes not?
What do the packages that have that restart requirement have in common? Is it not possible to update such a package without restart OS requirement?
If I am correct, sudo apt update; sudo apt upgrade
can also update/upgrade kernel. Does kernel update/upgrade also require OS restart?
Thanks.
I often keep my Ubuntu up indefinitely long, because I am always running some programs and I don't want to interrupt them.
debian ubuntu apt package-management
marked as duplicate by muru, Jeff Schaller, Stephen Kitt
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
18 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
1
Ask ubuntu developers. Restarting the upgraded program is enough, or all programs which depends on an upgraded library.
– Ipor Sircer
21 hours ago
3
It depends on what's being updated. When the kernel itself, kernel modules, or libraries are updated, it's best to reboot to make sure that applications and processes aren't broken by trying to reference older versions.
– Nasir Riley
21 hours ago
add a comment |
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
This question already has an answer here:
What forces a reboot?
2 answers
On Ubuntu, when running sudo apt update; sudo apt upgrade
, why sometimes it asks me to restart my OS and sometimes not?
What do the packages that have that restart requirement have in common? Is it not possible to update such a package without restart OS requirement?
If I am correct, sudo apt update; sudo apt upgrade
can also update/upgrade kernel. Does kernel update/upgrade also require OS restart?
Thanks.
I often keep my Ubuntu up indefinitely long, because I am always running some programs and I don't want to interrupt them.
debian ubuntu apt package-management
This question already has an answer here:
What forces a reboot?
2 answers
On Ubuntu, when running sudo apt update; sudo apt upgrade
, why sometimes it asks me to restart my OS and sometimes not?
What do the packages that have that restart requirement have in common? Is it not possible to update such a package without restart OS requirement?
If I am correct, sudo apt update; sudo apt upgrade
can also update/upgrade kernel. Does kernel update/upgrade also require OS restart?
Thanks.
I often keep my Ubuntu up indefinitely long, because I am always running some programs and I don't want to interrupt them.
This question already has an answer here:
What forces a reboot?
2 answers
debian ubuntu apt package-management
debian ubuntu apt package-management
edited 21 hours ago
asked 21 hours ago
Tim
24.7k70239433
24.7k70239433
marked as duplicate by muru, Jeff Schaller, Stephen Kitt
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
18 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by muru, Jeff Schaller, Stephen Kitt
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
18 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
1
Ask ubuntu developers. Restarting the upgraded program is enough, or all programs which depends on an upgraded library.
– Ipor Sircer
21 hours ago
3
It depends on what's being updated. When the kernel itself, kernel modules, or libraries are updated, it's best to reboot to make sure that applications and processes aren't broken by trying to reference older versions.
– Nasir Riley
21 hours ago
add a comment |
1
Ask ubuntu developers. Restarting the upgraded program is enough, or all programs which depends on an upgraded library.
– Ipor Sircer
21 hours ago
3
It depends on what's being updated. When the kernel itself, kernel modules, or libraries are updated, it's best to reboot to make sure that applications and processes aren't broken by trying to reference older versions.
– Nasir Riley
21 hours ago
1
1
Ask ubuntu developers. Restarting the upgraded program is enough, or all programs which depends on an upgraded library.
– Ipor Sircer
21 hours ago
Ask ubuntu developers. Restarting the upgraded program is enough, or all programs which depends on an upgraded library.
– Ipor Sircer
21 hours ago
3
3
It depends on what's being updated. When the kernel itself, kernel modules, or libraries are updated, it's best to reboot to make sure that applications and processes aren't broken by trying to reference older versions.
– Nasir Riley
21 hours ago
It depends on what's being updated. When the kernel itself, kernel modules, or libraries are updated, it's best to reboot to make sure that applications and processes aren't broken by trying to reference older versions.
– Nasir Riley
21 hours ago
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
It depends on what is running and being updated. The kernel needs to be restarted no matter what. If a main component gets updated such as glibc you may need to restart every application. If that is the case a reboot is the easiest. Run the update and type lsof | grep deleted
. You will see if the kernel is holding any of those files opened still.
New contributor
add a comment |
up vote
2
down vote
A reboot is rarely mandatory, even if notifications say so, but it is easier than restarting all the dependent services and applications. Examine the updated packages with apt-cache show [package name]
or apt changelog [package name]
, to decide if there are critical security updates, or if you can get by without them until reboot.
Since you mentioned having important programs running that you do not want to interrupt, I heard it is possible to livepatch kernel updates without rebooting, but the setup adds additional complexity and support, so distros don't automatically include it.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
It depends on what is running and being updated. The kernel needs to be restarted no matter what. If a main component gets updated such as glibc you may need to restart every application. If that is the case a reboot is the easiest. Run the update and type lsof | grep deleted
. You will see if the kernel is holding any of those files opened still.
New contributor
add a comment |
up vote
3
down vote
It depends on what is running and being updated. The kernel needs to be restarted no matter what. If a main component gets updated such as glibc you may need to restart every application. If that is the case a reboot is the easiest. Run the update and type lsof | grep deleted
. You will see if the kernel is holding any of those files opened still.
New contributor
add a comment |
up vote
3
down vote
up vote
3
down vote
It depends on what is running and being updated. The kernel needs to be restarted no matter what. If a main component gets updated such as glibc you may need to restart every application. If that is the case a reboot is the easiest. Run the update and type lsof | grep deleted
. You will see if the kernel is holding any of those files opened still.
New contributor
It depends on what is running and being updated. The kernel needs to be restarted no matter what. If a main component gets updated such as glibc you may need to restart every application. If that is the case a reboot is the easiest. Run the update and type lsof | grep deleted
. You will see if the kernel is holding any of those files opened still.
New contributor
New contributor
answered 21 hours ago
Ryan Young
311
311
New contributor
New contributor
add a comment |
add a comment |
up vote
2
down vote
A reboot is rarely mandatory, even if notifications say so, but it is easier than restarting all the dependent services and applications. Examine the updated packages with apt-cache show [package name]
or apt changelog [package name]
, to decide if there are critical security updates, or if you can get by without them until reboot.
Since you mentioned having important programs running that you do not want to interrupt, I heard it is possible to livepatch kernel updates without rebooting, but the setup adds additional complexity and support, so distros don't automatically include it.
add a comment |
up vote
2
down vote
A reboot is rarely mandatory, even if notifications say so, but it is easier than restarting all the dependent services and applications. Examine the updated packages with apt-cache show [package name]
or apt changelog [package name]
, to decide if there are critical security updates, or if you can get by without them until reboot.
Since you mentioned having important programs running that you do not want to interrupt, I heard it is possible to livepatch kernel updates without rebooting, but the setup adds additional complexity and support, so distros don't automatically include it.
add a comment |
up vote
2
down vote
up vote
2
down vote
A reboot is rarely mandatory, even if notifications say so, but it is easier than restarting all the dependent services and applications. Examine the updated packages with apt-cache show [package name]
or apt changelog [package name]
, to decide if there are critical security updates, or if you can get by without them until reboot.
Since you mentioned having important programs running that you do not want to interrupt, I heard it is possible to livepatch kernel updates without rebooting, but the setup adds additional complexity and support, so distros don't automatically include it.
A reboot is rarely mandatory, even if notifications say so, but it is easier than restarting all the dependent services and applications. Examine the updated packages with apt-cache show [package name]
or apt changelog [package name]
, to decide if there are critical security updates, or if you can get by without them until reboot.
Since you mentioned having important programs running that you do not want to interrupt, I heard it is possible to livepatch kernel updates without rebooting, but the setup adds additional complexity and support, so distros don't automatically include it.
answered 20 hours ago
hellork
665
665
add a comment |
add a comment |
1
Ask ubuntu developers. Restarting the upgraded program is enough, or all programs which depends on an upgraded library.
– Ipor Sircer
21 hours ago
3
It depends on what's being updated. When the kernel itself, kernel modules, or libraries are updated, it's best to reboot to make sure that applications and processes aren't broken by trying to reference older versions.
– Nasir Riley
21 hours ago