From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Doug McNaught <doug@mcnaught.org>
Cc: Muli Ben-Yehuda <mulix@mulix.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] new syscall to allow notification when arbitrary pids die
Date: Mon, 12 May 2003 10:07:19 -0400 [thread overview]
Message-ID: <3EBFAA97.6030804@nortelnetworks.com> (raw)
In-Reply-To: m3smrki9j3.fsf@varsoon.wireboard.com
Doug McNaught wrote:
> No reason to have one FD per process monitored. Just a single FD, to
> which you can write() a control string to to add or remove a process
> from the list, and for which read() yields a small data record
> describing the process event that just happened. It's a bit plan-9ish
> but there's nothing wrong with that...
Ah, okay. Interesting idea. It would get around the limitation of having to
use rt signals to get the queueing (though I'm not likely to hit that limit in
any case).
Have to think about that one...
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-05-12 13:55 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
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 [this message]
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=3EBFAA97.6030804@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=doug@mcnaught.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.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