3 ms·
Here's a system that runs a business that I put on "cruise control" 10 years ago. It just keeps on running with minimal attention ... Sun Microsystems Inc. S
by excitom 13y ago
Here's a system that runs a business that I put on "cruise control" 10 years ago. It just keeps on running with minimal attention ...
Sun Microsystems Inc. SunOS 5.8 Generic February 2000
DST Patches Applied Tue Mar 6 17:16:02 CST 2007
# uname -a
SunOS 5.8 Generic_108528-09 sun4u sparc SUNW,Ultra-60
# uptime
3:36pm up 811 day(s), 17 min(s), 3 users, load average: 0.63, 0.79, 0.74
- blhack 13y agoThat's really scary, man. What if the system tries to reboot and crashes on the way back up? It's happened to me before. Go reboot that damn thing!
- ygra 13y agoSo that it crashes now? ;-)
- eru 13y agoThat'll crash it when he has the time to look into it, and has backup handy. Not at a random time.
- excitom 13y agoThe last time it rebooted was due to a power glitch at the data center. Came back up just fine. Prior to that, uptime was over 1,000 days :-)
- Amadou 13y agoYou don't understand his point. He's saying, how do you know that the system hasn't acquired some sort of configuration/software/hardware degradation in the meantime that only manifests on boot? If you don't regularly exercise/test a critical function, then you substantially increase your risk that the critical function will fail when you really do need it. Q: What's the worst time to find out your system won't boot? A: Right after it crashed. You are better off with scheduled maintenance periods where you can reboot the server and it isn't critical if it fails. That gives you a chance to correct anything on your terms rather than fire-fighting.
- eru 13y agoCompare Crash-Only Software (https://en.wikipedia.org/wiki/Crash-only_software https://en.wikipedia.org/wiki/Crash-only_software or https://lwn.net/Articles/191059/ https://lwn.net/Articles/191059/).