4 ms·
Nope, sorry. I just can't accept this. I've though about it for 10 minutes trying to convince myself that this is a pragmatic approach to a difficult problem bu
by dazzawazza 17y ago
Nope, sorry. I just can't accept this. I've though about it for 10 minutes trying to convince myself that this is a pragmatic approach to a difficult problem but I just can't see it.
It's just poor management of servers. If you have a process that routinely leaks memory or stalls then manage that by restarting it & balancing it but rebooting the entire machine! This implies that you don't trust your OS to NOT leak resources (pipes, files, sockets, whatever) thus you need a new OS.
The 'excuse' that it forces you to build a scalable redundant system is bogus, it's folly.
- rm-rf 17y agoAnd - every time you re-boot you loose valuable data that could be used to determine the root cause of whatever is breaking the server OS. I've got a mantra that I have to repeat pretty often: "Re-booting is not a valid troubleshooting technique."