If apm is setup on your system and you need to shut down repeatedly you
could try suspending instead of shutting down.
Be aware that a large amount of the traffic on linux lists (and windoze) is
about devices not working after suspend so you might hit problems.
The other problem is that I always forget that I suspended my laptop and hit
the on/off button instead of the shift key to wake it up again.
Other than that it worked a treat for me on RH5.2 but I havent tried it yet
on RH6.0.
----- Original Message -----
From: Declan Moriarty <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 23 June 1999 18:33
Subject: Shutdown sequence - so long?
> Sender: [EMAIL PROTECTED]
> Received: from listserv.funet.fi (listserv.funet.fi [128.214.248.27])
> by hpamgaaa.compuserve.com (8.8.8/8.8.8/HP-1.5) with ESMTP id NAA03218
> for <[EMAIL PROTECTED]>; Wed, 23 Jun 1999 13:33:19 -0400 (EDT)
> Received: from vger.rutgers.edu ([128.6.190.2]:8736 "EHLO
vger.rutgers.edu" ident: "NO-IDENT-SERVICE[2]") by listserv.funet.fi with
ESMTP id <7795-29769>; Wed, 23 Jun 1999 20:26:32 +0300
> Received: by vger.rutgers.edu via listexpand id <S155620AbPFWQqs>; Wed, 23
Jun 1999 12:46:48 -0400
> Received: by vger.rutgers.edu id <S155292AbPFWQn5>; Wed, 23 Jun 1999
12:43:57 -0400
> Received: from munchkin.esatclear.ie ([194.145.128.10]:25016 "EHLO
munchkin.esatclear.ie") by vger.rutgers.edu with ESMTP id <S156209AbPFWQmz>;
Wed, 23 Jun 1999 12:42:55 -0400
> Received: from 586 (f-airlock225.esatclear.ie [194.145.135.225])
> by munchkin.esatclear.ie (8.8.7/8.8.7) with SMTP id RAA32215
> for <[EMAIL PROTECTED]>; Wed, 23 Jun 1999 17:42:53 +0100
> From: Declan Moriarty <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Shutdown sequence - so long?
> Date: Tue, 22 Jun 1999 21:19:56 +0000
> X-Mailer: KMail [version 0.7.9]
> Content-Type: text/plain; charset=US-ASCII
> MIME-Version: 1.0
> Message-Id: <99062221295902.00637@586>
> Content-Transfer-Encoding: 7BIT
> Sender: [EMAIL PROTECTED]
> Precedence: bulk
> X-Loop: [EMAIL PROTECTED]
> X-Orcpt: rfc822;linux-laptop-outgoing
>
>
>
> This may be heresy, but I am irritated by the amount of time
> linux spends shutting down. I am running SuSE 6.1, and I generally boot
> up, work, and close off, so it may happen a number of times a day.
> Linux (Heresy again) sits there thinking it is the central hub of a
> multitasking universe; these delusions of grandeur are all very well,
> and comforting to an op system, but I wonder what I could trim out of a
> closedown sequence something like the following, which is packed with
> pauses.
>
> Goung down for reboot NOW !!!
> Sending all processes the TERM signal
> Sending all processes the KILL signal
> Shuitting Down (each daemon is individually closed off, most of which
> are quite idle anyhow; somewhere between 6 and 12 of these on the
> average system I suppose)
> Sending all processes the TERM signal again
> Sending all processes the KILL signal again
> Then it runs a script /init.d/halt.local
> Unmounts all drives and /proc
>
> THEN it actually shuts down. I know the drives have to be dismounted.
> How much of the rest is really necessary? When I screw up and crash the
> thing, the only thing to suffer is drive integrity, and fsck wags its
> finger at me again. No program complains at all. The waiting states are
> surely unnecessary - it doesn't have to shut down a remote station on
> Mars, just itself.
>
> --
> Regards,
>
>
> Declan Moriarty
>
