From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "Sabharwal, Atul" <atul.sabharwal@intel.com>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [Announce] Non Invasive Kernel Monitor for threads/processes
Date: Wed, 16 Jun 2004 10:28:03 -0400 [thread overview]
Message-ID: <40D058F3.5070109@nortelnetworks.com> (raw)
In-Reply-To: <66539F0E7F15B44C9C0FC50D0FF024F7B1A324@orsmsx407>
Sabharwal, Atul wrote:
> How does auditing work in the event of a process failure ? There would
> be
> no system call triggered in that case. Also, my initial thoughts are
> that the non-invasive Kmonitor is lesser performance impact when
> compared
> to auditing. I would spend some time developing sample code to confirm
> it.
Just to put in my $.02. We developed a very simple (even simpler than Kmonitor
in that it didn't track fork/exec) way for a process to get notified when other
processes exited (properly or otherwise). We want to use this in the field for
a lifecycle monitoring function (a sort of super-init) so it needs to be as
lightweight as possible. I'd love to be able to use something from the mainline
kernel, but it has to be field-runnable without slowing stuff down.
Chris
next prev parent reply other threads:[~2004-06-16 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 0:54 [Announce] Non Invasive Kernel Monitor for threads/processes Sabharwal, Atul
2004-06-16 1:12 ` Chris Wright
2004-06-16 14:28 ` Chris Friesen [this message]
2004-06-16 17:36 ` Rusty Lynch
-- strict thread matches above, loose matches on Subject: below --
2004-06-15 22:48 Sabharwal, Atul
2004-06-15 18:38 Atul Sabharwal
2004-06-15 19:54 ` Atul Sabharwal
[not found] ` <40CF5D39.1060701@linux.jf.intel.com>
[not found] ` <20040615142304.5d9591d5.akpm@osdl.org>
2004-06-16 0:25 ` Atul Sabharwal
2004-06-16 1:01 ` Rusty Lynch
2004-06-16 0:39 ` Chris Wright
2004-06-16 12:32 ` Karim Yaghmour
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=40D058F3.5070109@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=atul.sabharwal@intel.com \
--cc=chrisw@osdl.org \
--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 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.