From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill(-1,sig)
Date: Mon, 17 Dec 2001 09:41:33 -0200 [thread overview]
Message-ID: <01121709413305.01828@manta> (raw)
In-Reply-To: <200112170701.fBH71uW04275@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200112170701.fBH71uW04275@vindaloo.ras.ucalgary.ca>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="PT 154", Size: 1214 bytes --]
On Monday 17 December 2001 05:01, Richard Gooch wrote:
> Hi, all. To followup on the change in 2.5.1 which sends a signal to
> the signalling process when send_pid==-1, I have a definate case where
> the new behaviour is highly undesirable, and I would say broken.
>
> shutdown(8) from util-linux (*not* the version that comes with the
> bloated monstrosity known as SysVInit) uses the sequence:
Hi Richard, I'm using your new init and happy with it (thanks!).
I am very willing to discuss other side of a coin (i.e. shutdown sequence),
let's do it off the list.
> kill (-1, SIGTERM);
> sleep (2);
> kill (-1, SIGKILL);
>
> to ensure that all processes not stuck in 'D' state are killed.
>
> With the new behaviour, shutdown(8) ends up killing itself. This is no
> good, because the shutdown process doesn't complete (i.e. unmounting
> of filesystems, calling sync(2) and good stuff like that).
I don't use your shutdown, I found it possible to spawn a shell script
in a new process group and use killall5 to term/kill everything except this
process group. It works. (But yesterday I saw fsck again... something did not
get umounted?) I can mail my scripts to you for a little discussion. Mail me.
--
vda
next prev parent reply other threads:[~2001-12-17 7:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 7:01 [PATCH] kill(-1,sig) Richard Gooch
2001-12-17 11:41 ` vda [this message]
2001-12-17 16:41 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2001-12-17 23:38 Andries.Brouwer
2001-12-14 21:22 Andries.Brouwer
2001-12-14 17:34 Andries.Brouwer
2001-12-14 20:25 ` Linus Torvalds
2001-12-17 9:34 ` Chris Wright
2001-12-17 14:41 ` vda
2001-12-17 11:53 ` Sean Hunter
2001-12-17 12:06 ` Matthew Kirkwood
2001-12-17 12:30 ` Sean Hunter
2001-12-17 12:16 ` Miquel van Smoorenburg
2001-12-17 16:06 ` vda
2001-12-14 20:36 ` Simon Kirby
2001-12-14 20:40 ` Linus Torvalds
2001-12-14 20:49 ` Simon Kirby
2001-12-15 10:19 ` Albert D. Cahalan
2001-12-15 14:03 ` Martin Josefsson
2001-12-15 23:09 ` Simon Kirby
2001-12-16 8:26 ` Albert D. Cahalan
2001-12-17 8:50 ` Helge Hafting
2001-12-17 20:51 ` Udo A. Steinberg
2001-12-17 21:13 ` Linus Torvalds
2001-12-17 22:06 ` Richard B. Johnson
2001-12-18 17:27 ` Alan Cox
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=01121709413305.01828@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.