Hello, Kt, 2015 01 08 11:32 -0600, Valeri Galtsev rašė: right: "snorkel" ;-) One of the pushing points was: already then on average every 30-45 days was either glibc or kernel update, meaning you have to reboot the box (and on multiple threads here there was a bunch of other unpleasant things mentioned so I'll skip them...). Linux from And your point? From my previous Linux Engineer experience in some small enterprise, being one of the top 5 biggest banks, there was a push to make mandatory scheduled server reboots every month or two. Rationale was simple: keeping long uptimes does not makes sense, when updates (not necessary OS but also userspace) piles up and after unexpected reboot shit happens as server is no longer able to boot. This was the experiences with various systems, including RHEL5 on x86 and IBM AIX on Power, Windows and other lovely bunch of hardware. As there were multiple incidents, it was decided to move to a mandatory reboot schedule to have maintenance windows. I believe the only system that was excluded from such plans was mainframe. Of course this requires to design systems to have load balancing, failover and other stuff available and working. So, several of those people fled to open solaris. My journey was different, I ended up migrating a bunch of most important boxes to FreeBSD. I know how many on this list are already allergic to me saying this, I promise, this is the last time. I'm using as excuse something familiar I feel in James's post... And does FreeBSD have magic bullet against reboot requirement after kernel/libc update? Or are you simply not patching system (which you can do on Linux too) ? BTW Linux already (again) procedes to rebootless kernel upgrade. Unfortunately now there are 4 different implementations (thanks goes to Oracle for buying KSplice and making this exclusive to OL). Although if my memory does not fail there were talks about unification. -- ____________________________________________________________ Elvinas Piliponis [cid:1420798946.4375.1.camel at ltkaude5005] Studentų g. 59-B707, LT-51365, Kaunas, Lietuva Email: elvinas.piliponis at virtustream.com<https://exchangevs.virtustream.com/owa/redir.aspx?C=C7sp-jyqTEeF3k7ArpiVF1dOSht06dEImQkOuwrkH1VgCkmkTLcZmzDuYzOe4cWdlcZqPVHpALo.&URL=mailto%3aelvinas.piliponis%40virtustream.com> | Mobile: +370 69807947 The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting the email and its attachments from all computers without copying or disclosing it.