On 09/10/17 21:55, Wolfgang Pfeiffer wrote: > On Sun, 2017-09-10 at 21:26 +0800, Ed Greshko wrote: >> On 09/10/17 21:03, Wolfgang Pfeiffer wrote: >>> On Sun, 2017-09-10 at 11:37 +0100, Patrick O'Callaghan wrote: >>>> On Sun, 2017-09-10 at 03:21 -0400, Bill Shirley wrote: >>>>> Just a couple of my servers: >>>>> [0:root@apinetstore2 ~]$ cat /etc/redhat-release >>>>> Fedora release 21 (Twenty One) >>>>> [0:root@apinetstore2 ~]$ uptime >>>>> 02:18:00 up 949 days, 17:08, 1 user, load average: 0.21, 0.41, 0.44 >>>>> >>>>> [0:root@elvis ~]$ cat /etc/redhat-release >>>>> Fedora release 16 (Verne) >>>>> [0:root@elvis ~]$ uptime >>>>> 02:19:02 up 553 days, 16:00, 4 users, load average: 0.20, 0.16, 0.14 >>>>> >>>>> It's usually a disk wearing out that forces a reboot. >>>> All that means is that you're running out-of-date systems on your >>>> servers. >>> It's also a strong hint that it's possible to have machines up and >>> running for >>> such a long time. >> Sure..... If you never do any updates! > I wouldn't recommend that: What I wanted to say, was: give us the updates, make > sure they're safely applied in a running system *and* remove the need to reboot. > And yes, I know this is stuff from a still distant future ... > IMO, you're making a mountain out of a mole hill. Don't want to do reboots "too" often (with "too often" being subjective) then don't update "too" often. Your system is up 24/7 and you are concerned about the few minutes of downtime while the rebooting is happening? Schedule the reboot while you're sleeping. You do sleep, yes? Or while you eat lunch. You must eat. You have systems providing vital services 24hrs/day to people outside of your local network and have service level agreements? Look into load balancing and/or fail-over systems so you can update one system while not affecting the service. Of course you do understand that the software provided by Linux distributions is open-source and written by a vast number of people with no central control. I mean there isn't a central authority that can demand and enforce the edict "remove the need to reboot". So, simply define your goals for how you want to maintain your system and develop your procedures to meet these goals. -- Fedora Users List - The place to go to speculate endlessly
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
