Disclaimer: Not a troll I'm curious as to this obsession with uptime is. All of the posts of this type are along the lines of "After X days, Y thing does not work but if I reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad form or something like that? I reboot every night whether it is needed or not, not afraid to admit it, and everything works fine for me.
We also do the "Sunday reboot" of all of our Windows servers as well as restarting all of the critical services such as IIS , SQL, Exchange etc nightly. It helps, a lot (Exchange is a notorious memory leaker) Of course, if your install processes calls 24/7 that's a different story. However, I expect that the majority of Asterisk installs are for a 9-to-5 type of operation. We run two shifts here, and we stop processing calls at 10 PM, and start again at about 6 AM - a large window of opportunity to reboot. Why not take advantage of it? I've also heard it said, something along the lines of: "If you have to reboot, your server isn't set up correctly" to which I say piffle. Even NASA has rebooted the Mars probes after they land and I understand that they run VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. 24/7/365 installs aside, is there a reason why reboots seem to be frowned upon? Again, not trolling, just curious. _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users