1 |
On Wed, Apr 2, 2008 at 12:19 PM, Dale <dalek1967@×××××××××.net> wrote: |
2 |
> |
3 |
> Volker Armin Hemmann wrote: |
4 |
> |
5 |
> > On Mittwoch, 2. April 2008, Steven Lembark wrote: |
6 |
> > |
7 |
> > |
8 |
> > > Liviu Andronic wrote: |
9 |
> > > > On Fri, Mar 28, 2008 at 10:07 AM, Dale <dalek1967@×××××××××.net> |
10 |
> wrote: |
11 |
> > > >>> By the way the safest and recommended command, although a bit |
12 |
> longish |
13 |
> > > >>> should be ALT+SysRq(or print)+S(ync)+U(mount)+B(Reboot). |
14 |
> > > >> |
15 |
> > > >> Since I wanted to shutdown instead of reboot, it would be ALT + |
16 |
> SysRq |
17 |
> > > >> + S + U + O then correct? |
18 |
> > > > |
19 |
> > > > Are there any potential harms to the hardware / system in case one |
20 |
> > > > tends to abuse (i.e. use more often than necessary) of this command? |
21 |
> > > > It's so often so tempting to shut down your system fast. |
22 |
> > > |
23 |
> > > Short of a serious emergency (e.g., UPS with |
24 |
> > > 30-sec lag and no input power) stick with |
25 |
> > > 'shutdown -fh now'. The main problem is that |
26 |
> > > you bypass the stop phase of all the app's |
27 |
> > > started up via init.d; very little short of |
28 |
> > > just hitting the reset switch or yanking the |
29 |
> > > power. |
30 |
> > > |
31 |
> > > |
32 |
> > |
33 |
> > if you do it the right way, start with 'e' and 'i', all apps are cleanly |
34 |
> terminated/killed. So if an app does not quit cleanly, it is broken. |
35 |
> > |
36 |
> > The correct sequence is: e,i,u,b/o and it is absolutly save. |
37 |
> > |
38 |
> > |
39 |
> |
40 |
> |
41 |
> Folks, keep in mind why I asked this question in the first place. My power |
42 |
> supply was frying and I needed a VERY fast shutdown. This was not asked as |
43 |
> a fast way to shutdown just because we are impatient or something. This was |
44 |
> for the event of a serious emergency where I needed a shutdown in just a |
45 |
> very few seconds not a minute or two. Some of my services take a while to |
46 |
> stop, foldingathome being the longest one. |
47 |
> |
48 |
> Basically, this is not intended to be used to shutdown a puter on a regular |
49 |
> basis, unless you burn out P/S's on a daily basis. O-o |
50 |
> |
51 |
> Just didn't want someone to be using this on a regular basis and then |
52 |
> wondering why their system has a new nickname, FUBAR. :'( |
53 |
> |
54 |
> Dale |
55 |
> |
56 |
> :-) :-) |
57 |
> |
58 |
|
59 |
Understood. I think it sort of morphed into something more general, |
60 |
like what to do when the rest of us run into the occasional problem we |
61 |
all run into. Yesterday our MythTV backend server crashed 4 times. It |
62 |
hung completely killing X, etc. and I was in need of a good way to |
63 |
bring the machine down. I found this topic both timely and helpful, at |
64 |
least for future problems. |
65 |
|
66 |
Cheers, |
67 |
Mark |
68 |
-- |
69 |
gentoo-user@l.g.o mailing list |