From: Erich Focht <efocht@hpce.nec.com>
To: lse-tech@lists.sourceforge.net
Cc: Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
elsa-announce <elsa-announce@lists.sourceforge.net>,
elsa-devel <elsa-devel@lists.sourceforge.net>,
Gerrit Huizenga <gh@us.ibm.com>,
Jean Pierre Dion <jean-pierre.dion@bull.net>,
"lse-tech@lists.sourceforge.net" <lse-tech@lists.sourceforge.net>
Subject: Re: [Lse-tech] [RFC] fork historic module
Date: Fri, 17 Dec 2004 18:39:07 +0100 [thread overview]
Message-ID: <200412171839.07927.efocht@hpce.nec.com> (raw)
In-Reply-To: <1103295512.7329.75.camel@frecb000711.frec.bull.fr>
On Friday 17 December 2004 15:58, Guillaume Thouvenin wrote:
> Here is the fork historic module. This module keeps the historic about
> the creation of processes and it gives this information to a user space
> application if one is registered. Currently, only one application can
> use it. If needed it could be extended to several applications.
This sounds very useful for a lot of interesting stuff. Though in the
current form maybe the name is not appropriate: the module doesn't
keep track of the fork history, this would be done in user-space. The
module is more like a relay for fork monitoring.
If you plan to extend this to multiple registered user space processes
it would be great to have per process reporting policies, for example:
- all forks,
- only forks of descendants (children, etc).
Erich
next prev parent reply other threads:[~2004-12-17 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 14:58 [RFC] fork historic module Guillaume Thouvenin
2004-12-17 15:11 ` [Lse-tech] " Andi Kleen
2004-12-20 7:28 ` Guillaume Thouvenin
2004-12-17 15:24 ` David Vrabel
2004-12-17 17:06 ` Randy.Dunlap
2004-12-17 17:39 ` Erich Focht [this message]
2004-12-17 16:52 [Lse-tech] " Manfred Spraul
2004-12-17 16:59 ` Andi Kleen
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=200412171839.07927.efocht@hpce.nec.com \
--to=efocht@hpce.nec.com \
--cc=akpm@osdl.org \
--cc=elsa-announce@lists.sourceforge.net \
--cc=elsa-devel@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=guillaume.thouvenin@bull.net \
--cc=jean-pierre.dion@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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.