Upgraded packages that require a restart
klarsen1 at gmail.com
Fri Oct 8 18:22:03 UTC 2010
On 10/08/2010 09:35 AM, NoOp wrote:
> On 10/08/2010 04:47 AM, R Kimber wrote:
>> Is there a definitive list somewhere that shows which packages, when
>> upgraded, require you to restart the computer? Long ago, it used to be just
>> the kernel, but now it seems to embrace various packages. It would help if
>> the upgrade manager announced clearly, before you upgrade, that a restart is
>> required if you go ahead, but it doesn't.
>> If there isn't a webpage somewhere, maybe it would be useful if this list
>> compiled one (?). I'm guessing, but a start might be:
> I think that it depends on the patch, so it's hard to determine. For
> security updates the USN announcement will show whether a reboot is
> required, example:
> After a standard system update you need to reboot your computer to make
> all the necessary changes.
> But who goes and reads those... particularly when the USN isn't
> mentioned in the update description (only the CVE-2010-2939 is mentioned
> in the update-manager changes)?
> Probably the best method would be to add 'Reboot Required' in the
> update-manager listing *and* 'Description of update|Changes' section. At
> least that way you'd be able to un-tick' the update until you're ready.
> Of course, you don't need to reboot immediatly after the update, the
> changes just won't take effect until you do. File a wishlist bug on
> launchpad. That wouldn't help with 'apt-get/aptitude' update/upgrade's,
I use the normal update manager to appear, and then tell it to
complete updates. At the end it sometimes says "Reboot Required" and
there is a button there to cause a reboot. I often use the button
because my computer stays on for weeks at a time. I am certain the guys
who set up the upgrade know what is right. So it does work quite well.
Karl F. Larsen, AKA K5DI
Key ID = 3951B48D
More information about the ubuntu-users