From: Doug McNaught <doug@mcnaught.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
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: 11 May 2003 23:32:29 -0400 [thread overview]
Message-ID: <m3y91cj0vm.fsf@varsoon.wireboard.com> (raw)
In-Reply-To: Chris Friesen's message of "Sun, 11 May 2003 23:26:06 -0400"
Chris Friesen <cfriesen@nortelnetworks.com> writes:
> > 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?
>
> Its cheaper and faster. It only costs a single call for each process,
> and then you get notified immediately when it dies.
Rather than a new syscall, what about a magic file or device that you
can poll()?
-Doug
next prev parent reply other threads:[~2003-05-12 3:19 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 [this message]
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=m3y91cj0vm.fsf@varsoon.wireboard.com \
--to=doug@mcnaught.org \
--cc=cfriesen@nortelnetworks.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.