From: splite-gentoo@sigint.cs.purdue.edu
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] strange gentoo shutdown sequence
Date: Mon, 3 May 2004 11:24:36 -0500 [thread overview]
Message-ID: <20040503162436.GA1938@sigint.cs.purdue.edu> (raw)
In-Reply-To: <20040502173223.GA7160@linux1.home>
On Sun, May 02, 2004 at 12:32:23PM -0500, William Hubbs wrote:
> Hi all,
>
> On Sun, May 02, 2004 at 01:40:08PM +0200, Sven K?hler wrote:
> > hi,
> >
> > gentoo usually does the following if i execute halt or reboot:
> >
> > sending all processes the TERM signal
> > sending all processes the KILL signal
> > stopping xdm ...
> > stopping alsasound ...
> > etc....
> >
> > in may eyes, this has to be the other way round:
> > first shutdown all deamons properly with the init.d-script, and than
> > send the remaining processes the TERM and KILL signals.
> >
> >
> > why does gentoo handle things the way it does? redhat etc. do it the
> > other way i described. using the init.d-script sounds more resonable to me.
>
> I just confirmed this. When you do a shutdown or a reboot or halt, the processes are killed by the kill and term signals before the services are actually stopped with the /etc/init.d/* scripts.
>
> Is there a reason for this or should it be the other way around?
init(8) itself sends the TERM and KILL signals when changing runlevels, and
there's no way around that, save patching init.
It's not a real problem because init only signals processes still in init's
process group, and there usually aren't any. (Run "ps -eo pid,pgrp,cmd" to
see if any are, if you're curious.)
"man init" for more info.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-05-03 16:24 UTC|newest]
Thread overview: 22+ 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 [this message]
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
2004-05-07 17:53 ` splite-gentoo
2004-05-04 16:28 ` Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2004-05-02 11:40 [gentoo-dev] " Sven Köhler
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=20040503162436.GA1938@sigint.cs.purdue.edu \
--to=splite-gentoo@sigint.cs.purdue.edu \
--cc=gentoo-dev@lists.gentoo.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