On Friday 11 December 2009 18:33:49 Mike Edenfield wrote: > On 12/11/2009 9:38 AM, Dale wrote: > > Mickaël Bucas wrote: > >> From the process name, you can deduce the service and restart it. > >> I've never needed a reboot for this kind of problem. > >> You may have to switch to run level 1 to restart some important > >> services like udev. > > > > Actually, you can kill udev and restart it. Kill the process and then > > run "/sbin/udevd --daemon" and it will be started again. > > Yeah, or you could, you know, just reboot. > > Frankly I have never figured out the irrational fear Linux people have > about rebooting their machines after a big upgrade. It takes my laptop > way less time to shutdown and restart than it does for me to manually > stop and restart everything that just got updated, and I can go grab a > soda in the meantime.
That's a laptop. Do you have an SLA with customers where you guarantee your laptop will be up 99.999%? My database and DNS servers do, and just in case you were asking, those 5 nines INCLUDES scheduled downtime. Unlike some other machines around in the company like, gee, I dunno, the Windows machines hosting the Active Directory, maybe? For some obscure perverse reason akin to grey elephants in the living room, those have 20 minutes downtime every single Friday. If I did that with my *nix boxes, I can pretty much kiss my plans for Christmas Bonus goodbye. Now do you understand why my refusal to reboot my machines willy-nilly is entirely rational? It's because they are not my laptop. -- alan dot mckinnon at gmail dot com
