how do i know i need a reboot after a console based "upgrade"?

[James Gray]

Tomoki Taniguchi wrote:
> when updating a system with the newest packages using the desktop
> tools like synaptic,
> if a package is upgraded that requires a reboot to take effect,
> there is a little icon that shows up on the upper panel to let me know
> i need to reboot.
> 
> 
> on a server system,  if i do a "sudo apt-get upgrade" or "sudo aptitude upgrade"
> is there anyway to know i need a reboot?

If the kernel is updated, reboot.
If a kernel module is updated, and you're using it, either reload the 
module (sometimes not possible, eg, storage controller which has the 
volume for the root partition), then reboot.

As a secondary thing, I usually reboot after a libc update too, as so 
many things rely on it you may as well reboot to make sure everything 
that relies on it is restarted.  However, unless it's a major version 
update, the system should continue to run without any problems - just 
anything that is already running, probably wont pick up the changed libc 
(which is probably a bug or security fix unless you're moving from one 
release to another).

So in short:
Kernel, kernel module and libc updates, reboot (unless you know what 
you're doing).  Anything else, just restart the updated program if it is 
already running.

Maybe get a book on system administration or read some the online 
guides.  If you're managing a server, I think you'd gain some valuable 
tips :)

Cheers,

James
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3253 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20070419/2a354cd3/attachment.bin>