I read somewhere that it is wise to reboot when you install or modify services that start upon boot. This way, if anything doesn't start right, you'll have a pretty good indication that it's due to whatever you were working on, and you'll know about it while the details are still fresh in your mind.
Of course you'll draw the line depending on how critical the service is, and how inconvenient a reboot is. I've just installed webmail on one of my servers. I've made a mental note to reboot "one of these days". If we get a power cycle between now and then it will be pretty obvious, and I can always start it remotely via ssh. Otherwise, I love your idea of a reboot every April Fools day :-) 210 days is very nice. Keep up the good work! Michael On Sat, 27 Nov 2004, Dan Barker wrote: > Excuse the bandwidth, but someone on this list is going to know. I've always > tried to reboot windoze boxes at least monthly. Back in "the day", I'd > reboot IBM mainframes each Standard/Daylight Savings transition, just > because I had to be on-site on a Sunday anyhow. No real reason. > > What's the thinking for Linux? I'm just running a couple daemons in support > of my Wireless Network subscription services (they diddle the firewall based > on Credit Card income) and the firewall. > > I was thinking that maybe I should reboot every April Fools day????? > > tia, Dan > > Top begins: > > 09:22:36 up 210 days, 4:32, 3 users, load average: 0.16, 0.30, 0.32 > 93 processes: 76 sleeping, 1 running, 16 zombie, 0 stopped > CPU states: 0.1% user 1.1% system 0.0% nice 0.0% iowait 98.6% idle > Mem: 256124k av, 250036k used, 6088k free, 0k shrd, 24000k > buff > 131228k active, 70640k inactive > Swap: 240932k av, 27616k used, 213316k free 131168k > cached > >
