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