From: Sean Hunter <sean@dev.sportingbet.com>
To: Matthew Kirkwood <matthew@hairy.beasts.org>
Cc: vda <vda@port.imtp.ilyichevsk.odessa.ua>,
Chris Wright <chris@wirex.com>,
Linus Torvalds <torvalds@transmeta.com>,
Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill(-1,sig)
Date: Mon, 17 Dec 2001 12:30:45 +0000 [thread overview]
Message-ID: <20011217123045.D14112@dev.sportingbet.com> (raw)
In-Reply-To: <20011217115344.C14112@dev.sportingbet.com> <Pine.LNX.4.33.0112171205590.10824-100000@sphinx.mythic-beasts.com>
In-Reply-To: <Pine.LNX.4.33.0112171205590.10824-100000@sphinx.mythic-beasts.com>; from matthew@hairy.beasts.org on Mon, Dec 17, 2001 at 12:06:30PM +0000
Doh!</slaps head>
Sean
On Mon, Dec 17, 2001 at 12:06:30PM +0000, Matthew Kirkwood wrote:
> On Mon, 17 Dec 2001, Sean Hunter wrote:
>
> > > Hmm. Looking at killall5 source I see
> > >
> > > kill(-1, STOP);
> > > for(each proc with p.sid!=my_sid) kill(proc, sig);
> > > kill(-1, CONT);
> > >
> > > I guess STOP will stop killall5 too? Not good indeed.
>
> > Couldn't it just do:
> [..]
> > ... in other words, block signals, do the killing, then unblock?
>
> SIGSTOP and SIGKILL can't be blocked.
>
> Matthew.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-12-17 12:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 17:34 [PATCH] kill(-1,sig) 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-12-14 21:22 Andries.Brouwer
2001-12-17 7:01 Richard Gooch
2001-12-17 11:41 ` vda
2001-12-17 16:41 ` Richard Gooch
2001-12-17 23:38 Andries.Brouwer
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=20011217123045.D14112@dev.sportingbet.com \
--to=sean@dev.sportingbet.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=chris@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@hairy.beasts.org \
--cc=torvalds@transmeta.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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