From: Ingo Oeser <ioe-lkml@rameria.de>
To: Albert Cahalan <albert@users.sf.net>
Cc: bruce@perens.com, Linus Torvalds <torvalds@osdl.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Never mind. Re: Signal left blocked after signal handler.
Date: Thu, 27 Nov 2003 10:11:51 +0100 [thread overview]
Message-ID: <200311271012.07893.ioe-lkml@rameria.de> (raw)
In-Reply-To: <1069883580.723.416.camel@cube>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 26 November 2003 22:53, Albert Cahalan wrote:
[2.4 vs. 2.6 wrt. thread synchronous signals]
> How about making the process sleep in a killable state?
>
> This is as if the blocking was obeyed, but doesn't
> burn CPU time. Only a debugger should be able to
> tell the difference.
This has 2 problems:
1) Servers and PID files or servers and simple monitoring software.
2) Processes spawned from init, which will not respawn.
Regards
Ingo Oeser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/xb/mU56oYWuOrkARAmNaAKCL1uojbOpMtMdSvAl6B9rBW51CTgCgypP8
NlbaIac25oefxcHL9WlzxyE=
=h6UI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-11-27 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 21:53 Never mind. Re: Signal left blocked after signal handler Albert Cahalan
2003-11-27 9:11 ` Ingo Oeser [this message]
2003-11-27 15:45 ` Albert Cahalan
2003-11-27 17:26 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 17:39 Bruce Perens
2003-11-26 17:55 ` Linus Torvalds
[not found] ` <3FC4ED5F.4090901@perens.com>
[not found] ` <3FC4EF24.9040307@perens.com>
[not found] ` <3FC4F248.8060307@perens.com>
2003-11-26 18:45 ` Never mind. " Linus Torvalds
2003-11-26 19:04 ` Bruce Perens
2003-11-26 19:14 ` Linus Torvalds
2003-11-26 19:52 ` Jamie Lokier
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=200311271012.07893.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=albert@users.sf.net \
--cc=bruce@perens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).