From: Miquel van Smoorenburg <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill(-1,sig)
Date: Mon, 17 Dec 2001 12:16:40 +0000 (UTC) [thread overview]
Message-ID: <9vknn8$e6g$1@ncc1701.cistron.net> (raw)
In-Reply-To: <UTC200112141734.RAA20953.aeb@cwi.nl> <20011217013445.A30669@figure1.int.wirex.com> <01121712412100.02022@manta> <20011217115344.C14112@dev.sportingbet.com>
In article <20011217115344.C14112@dev.sportingbet.com>,
Sean Hunter <sean@dev.sportingbet.com> wrote:
>On Mon, Dec 17, 2001 at 12:41:21PM -0200, vda wrote:
>> Hmm. Looking at killall5 source I see
>>
>> kill(-1, STOP);
>> I guess STOP will stop killall5 too? Not good indeed.
>>
>Couldn't it just do:
>
>sigprocmask (SIG_BLOCK, &new, &savemask);
>... in other words, block signals, do the killing, then unblock?
You can't block SIGSTOP and SIGKILL
Mike.
--
Deadlock, n.:
Deceased rastaman.
next prev parent reply other threads:[~2001-12-17 12:17 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
2001-12-17 12:16 ` Miquel van Smoorenburg [this message]
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='9vknn8$e6g$1@ncc1701.cistron.net' \
--to=miquels@cistron.nl \
--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