From: Muli Ben-Yehuda <mulix@mulix.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] new syscall to allow notification when arbitrary pids die
Date: Sat, 10 May 2003 10:38:42 +0300 [thread overview]
Message-ID: <20030510073842.GA31003@actcom.co.il> (raw)
In-Reply-To: <3EBC9C62.5010507@nortelnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Sat, May 10, 2003 at 02:29:54AM -0400, Chris Friesen wrote:
> I see two immediate uses for this. One would be to enable a "watcher"
> process which can do useful things on the death of processes which
> registered with it (logging, respawning, notifying other processes,
> etc).
Do it from user space, kill(pid, 0), check for ESRCH. I might see the
benefit of a new system call if it was synchronous (wait() semantics),
but since signal delivery is asynch anyway....
> The second would be to enable mutual
> suicide pacts between processes. (I'm not sure when I would use this, but
> it sounds kind of fun.)
Same thing, kill(pid, 0).
> Anyone have any opinions on this?
There's already a well established way to do what you want (get
non-immediate notification of process death). What benefit would your
approach give?
--
Muli Ben-Yehuda
http://www.mulix.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-10 7:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 6:29 [RFC] new syscall to allow notification when arbitrary pids die Chris Friesen
2003-05-10 7:38 ` Muli Ben-Yehuda [this message]
2003-05-12 3:26 ` Chris Friesen
2003-05-12 3:32 ` Doug McNaught
2003-05-12 3:42 ` Posible memory leak!? Boris Kurktchiev
2003-05-12 11:17 ` Boris Kurktchiev
[not found] ` <200305131158.h4DBw2u30860@Port.imtp.ilyichevsk.odessa.ua>
2003-05-13 18:17 ` Boris Kurktchiev
2003-05-12 18:06 ` Greg KH
2003-05-12 4:33 ` [RFC] new syscall to allow notification when arbitrary pids die Chris Friesen
2003-05-12 13:23 ` Doug McNaught
2003-05-12 14:07 ` Chris Friesen
2003-05-12 3:53 ` Frank Cusack
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=20030510073842.GA31003@actcom.co.il \
--to=mulix@mulix.org \
--cc=cfriesen@nortelnetworks.com \
--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