public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Young <ayoung@google.engr.sgi.com>
To: ghoward@sgi.com (Greg Howard)
Cc: hch@lst.de (Christoph Hellwig),
	davem@davemloft.net, linux-kernel@vger.kernel.org (LKML),
	ayoung@sgi.com (Aaron Young)
Subject: Re: Standardize shutdown of the system from enviroment control
Date: Tue, 9 Aug 2005 14:36:53 -0700 (PDT)	[thread overview]
Message-ID: <200508092136.OAA13698@google.engr.sgi.com> (raw)
In-Reply-To: <Pine.SGI.4.58.0508091619180.19699@gallifrey.americas.sgi.com> from "Greg Howard" at Aug 09, 2005 04:25:39 PM

> 
> 
> On Tue, 9 Aug 2005, Christoph Hellwig wrote:
> 
> > Currently snsc_event for Altix systems sends SIGPWR to init (and abuses
> > tasklist_lock..) while the sbus drivers call execve for /sbin/shutdown
> > (which is also ugly, it should at least use call_usermodehelper)
> > With normal sysvinit both will end up the same, but I suspect the
> > shutdown variant, maybe with a sysctl to chose the exact path to call
> > would be cleaner.  What do you guys think about adding a common function
> > to do this.
> 
> Sounds reasonable to me.  I'll copy Aaron Young, who I think
> actually wrote the code to send the SIGPWR, in case he had a Good
> Reason for doing it this way.  (Aaron, if I'm remembering wrong
> and you're not the guy who wrote this, let me know...)

  Yep, that was me. I couldn't really find a better way to do it at
  the time. An 'execve shutdown' probably would have been better in retrospect
  because I think sending SIGPWR to init doesn't always shutdown the machine.
  It depends on how some config files are setup (inittab, powerfail).
  I'd rather not depend on any config files and just force a shutdown/poweroff.

> 
> > Could you test such a patch for me?
> 
> Sure.  I'll need to get hold of some hardware/firmware that will
> reproduce a critical environmental situation...  Might take a
> litte while...

 Testing should be easy - on a Deskside Prism system, just hit the
 power button while up at Linux.

  reply	other threads:[~2005-08-09 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 21:10 Standardize shutdown of the system from enviroment control modules Christoph Hellwig
2005-08-09 21:25 ` Greg Howard
2005-08-09 21:36   ` Aaron Young [this message]
2005-08-11 12:10 ` Pavel Machek
2005-08-11 17:37 ` [PATCH, RFC] " Christoph Hellwig
2005-08-26 11:44   ` Christoph Hellwig
2005-08-26 12:22     ` Greg Howard
2005-08-27 13:16       ` Denis Vlasenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200508092136.OAA13698@google.engr.sgi.com \
    --to=ayoung@google.engr.sgi.com \
    --cc=ayoung@sgi.com \
    --cc=davem@davemloft.net \
    --cc=ghoward@sgi.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox