I'd say reboot when you do a kernel update, no more, no less.  There's no point
in doing kernel updates if you don't reboot (you're updating the disk and not
the memory).
If you wanna boot less often you might as well put kernel on the ignore list.

Don't let it be a pride thing.  If the machine causes no one to suffer when it's
rebooted then reboot all you like.  Realistically there are probably only two
situations where rebooting is an annoyance:  Crucial servers that are in
constant or almost constant use.  Workstations, where a reboot means someone
has to get their workflow back up.  A small home server (where the main user is
often the admin) could be rebootted hourly and the world would still turn just
as fast ;).

So, the answer is:  Reboot when you like.  It's my guess that the security
situation around this machine is excellent (on its own subnet, over home
broadband to the net), and it's not a mission critical machine for anyone.  So,
if your ego likes big numbers, the old kernel probably won't get you into any
trouble (do you have untrusted local users?).  And if you're paranoid or prefer
staying up to date, reboot when there's a kernel update.


That's my 2 cents.

Quoting Derek Carlson <[EMAIL PROTECTED]>:

> Hi,
> 
> I am torn.
> 
> This particular Arch configured PC has been up and running for, now, 49 
> days.  During that time, the system was upgraded at least 6 times.  It 
> is kept in sync with the testing repository, and I have some software 
> installed from extra.  The version of ndiswrapper that I use is compiled 
> by hand, so occasionally, I recompile the module if I notice that gcc or 
> the kernel has been updated.
> 
> Aside from that, this is a pretty vanilla system.  It provides file and 
> print services to a couple other PCs on a home network.
> 
> The question I have is this.
> 
> How often do people reboot their systems as a matter of maintenance? 
> 
> During the period of udev upgrades, I booted pretty regularly to make 
> sure I'd made all of the necessary changes.  The upgrades went smoothly 
> and without issue, btw.
> 
> I don't want to get to far away from what's fresh and current in the 
> wiki, forums and discussion thread, so it seems that a periodic hard 
> start may be useful as a matter of course.
> 
> Pride gets in the way, however, and I'd like top to show a 3 digit up 
> time someday! :-)
> 
> Thx in advance for any advice you can share.
> 
> Kind regards,
> 
> Derek
> 
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
> 




_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to