4 ms·
Personally, I'd rather just fix the problem :) :~$ uname -r && uptime 3.2.0-4-amd64 01:33:09 up 461 days, 3:50, 13 users,
by esaym 11y ago
Personally, I'd rather just fix the problem :)
:~$ uname -r && uptime
3.2.0-4-amd64
01:33:09 up 461 days, 3:50, 13 users,
- MichaelGG 11y agoDo you hot patch things or what?
- ucho 11y agoThere is/was KSplice for kernel and everything else can be upgraded without reboot.
- wereHamster 11y agoAnd what do you do when the machine goes down? How do you test that all services come back up again? Your infrastructure should be resilient against servers and services going down. But you can't test that if they never go down. See Netflix chaos monkey, or CoreOS automatically restarting after updates (which are rather frequent, every couple weeks).
- jdiez17 11y agoNice try :P # uptime 14:34:38 up 587 days, 21:12, 1 user, load average: 0.00, 0.00, 0.00
- keithpeter 11y agoGrandparent wins on users (13 times 400+ days) Seriously: I'm assuming that these are both servers running a single application or small group of related applications. OA was talking mainly about client style devices.