public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: splite-gentoo@sigint.cs.purdue.edu
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: strange gentoo shutdown sequence
Date: Fri, 07 May 2004 12:33:29 -0400	[thread overview]
Message-ID: <1083947609.9268.5.camel@localhost> (raw)
In-Reply-To: <20040504162509.GD7040@sigint.cs.purdue.edu>

On Tue, 2004-05-04 at 12:25, splite-gentoo@sigint.cs.purdue.edu wrote:
> On Tue, May 04, 2004 at 05:59:25PM +0200, Sven K?hler wrote:
> > >I don't know; I don't use RHL or RHEL.  However, I suspect they work just
> > >as Gentoo does.  init(8) first signals the processes in its process group,
> > >so you'll see:
> > >
> > >INIT: Switching to runlevel 0
> > >INIT: Sending processes the TERM signal
> > >INIT: Sending processes the KILL signal
> > >
> > >on the console.  Then init runs the RHL shutdown scripts, the final one of
> > >which probably sends all processes SIGTERM and SIGKILL, just like Gentoo's
> > >/etc/init.d/halt.sh does.
> > 
> > No, you first see the init-scripts shutting down all the services, and 
> > than you see the TERM/KILL stuff.
> 
> *shrug*  Maybe they kludged init so they wouldn't get support calls asking
> why processes were being killed before the shutdown scripts ran.

It is patched out.  I used to do the same thing with Slackware/LFS boxes
simply because it made for fewer questions from users.  You can always
grab the .src.rpm and look at what patches they use yourself.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a pengiun?


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-07 16:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 17:32 [gentoo-dev] strange gentoo shutdown sequence William Hubbs
2004-05-03  5:10 ` John Nilsson
2004-05-03  6:15   ` Olivier Crête
2004-05-03  6:46     ` John Nilsson
2004-05-03 17:22       ` Grant Goodyear
2004-05-03  8:30     ` Paul de Vrieze
2004-05-03  8:50       ` Allen D Parker
2004-05-03  9:05         ` Paul de Vrieze
2004-05-05 18:11           ` Martin Schlemmer
2004-05-03 16:24 ` splite-gentoo
2004-05-04 15:13   ` [gentoo-dev] " Sven Köhler
2004-05-04 15:33     ` splite-gentoo
2004-05-04 16:00       ` Sven Köhler
2004-05-04 16:30         ` Jon Portnoy
2004-05-04 15:16   ` Sven Köhler
2004-05-04 15:37     ` splite-gentoo
2004-05-04 15:59       ` Sven Köhler
2004-05-04 16:25         ` splite-gentoo
2004-05-07 16:33           ` Chris Gianelloni [this message]
2004-05-07 17:53             ` splite-gentoo
2004-05-04 16:28         ` Daniel Drake

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=1083947609.9268.5.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=splite-gentoo@sigint.cs.purdue.edu \
    /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