From: Al Boldi <a1426z@gawab.com>
To: coywolf@gmail.com
Cc: linux-assembly@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-smp@vger.kernel.org
Subject: Re: Fork capture
Date: Mon, 19 Sep 2005 18:01:47 +0300 [thread overview]
Message-ID: <200509191801.47546.a1426z@gawab.com> (raw)
In-Reply-To: <2cd57c9005091823551e49bc23@mail.gmail.com>
Coywolf Qi Hunt wrote:
> On 9/18/05, Al Boldi <a1426z@gawab.com> wrote:
> > Is there a way to capture a process-fork?
> >
> > Something like:
> > process/kModule A monitors procs for forking, captures it and manages
> > further processing.
>
> Look at the fork_connector patch.
Nice, but how could this be used to _manage_ further process-execution?
Also, would a user-space solution be possible?
Thanks!
--
Al
prev parent reply other threads:[~2005-09-19 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 14:48 Fork capture Al Boldi
2005-09-19 6:55 ` Coywolf Qi Hunt
2005-09-19 15:01 ` Al Boldi [this message]
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=200509191801.47546.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=coywolf@gmail.com \
--cc=linux-assembly@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@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;
as well as URLs for NNTP newsgroup(s).