From: Chris Friesen <cfriesen@nortel.com>
To: Valdis.Kletnieks@vt.edu
Cc: Robert Love <rml@novell.com>,
Nick Piggin <nickpiggin@yahoo.com.au>, Zach Brown <zab@zabbo.net>,
linux-kernel@vger.kernel.org,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
John McCutchan <ttb@tentacle.dhs.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] inotify, improved.
Date: Fri, 17 Jun 2005 10:36:03 -0600 [thread overview]
Message-ID: <42B2FBF3.6010607@nortel.com> (raw)
In-Reply-To: <200506171611.j5HGBFY8012609@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> It's also racy as hell. By the time the inotify gets delivered to the
> userspace process, pid 820 may be long gone.....
Yep. But I can see uses for people to want to log all activity on
specific directory trees. Think audit trails, etc.
Imagine root getting a log like:
Date: Jan 1,2006: file /foo/evidence.txt changed by user blah, pid
<666>, commandline: "vi evidence.txt"
Chris
next prev parent reply other threads:[~2005-06-17 16:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:18 [patch] inotify Robert Love
2005-06-16 17:52 ` Zach Brown
2005-06-16 18:25 ` Robert Love
2005-06-17 1:30 ` Nick Piggin
2005-06-17 1:35 ` Robert Love
2005-06-17 15:15 ` [patch] inotify, improved Robert Love
2005-06-17 15:37 ` Chris Friesen
2005-06-17 15:44 ` Robert Love
2005-06-17 16:11 ` Valdis.Kletnieks
2005-06-17 16:29 ` Robert Love
2005-06-17 16:36 ` Chris Friesen [this message]
2005-06-17 16:43 ` Chris Wright
2005-06-17 16:46 ` Muli Ben-Yehuda
2005-06-17 16:40 ` Chris Friesen
2005-06-17 17:57 ` John McCutchan
2005-06-17 17:20 ` Zach Brown
2005-06-17 17:54 ` John McCutchan
2005-06-17 17:56 ` Zach Brown
2005-06-17 18:15 ` John McCutchan
2005-06-17 18:17 ` Zach Brown
2005-06-17 17:07 ` [patch] inotify Arnd Bergmann
2005-06-17 17:54 ` Christoph Hellwig
2005-06-17 18:12 ` John McCutchan
2005-06-17 18:16 ` Robert Love
2005-06-17 18:28 ` Christoph Hellwig
2005-06-17 18:38 ` Robert Love
2005-06-17 18:45 ` Christoph Hellwig
2005-06-17 18:54 ` Robert Love
2005-06-17 17:56 ` John McCutchan
2005-06-17 21:33 ` Andrew Morton
2005-06-17 21:40 ` Robert Love
2005-06-17 23:52 ` Robert Love
2005-06-21 0:51 ` Neil Brown
2005-06-21 2:15 ` John McCutchan
2005-06-21 2:29 ` Neil Brown
2005-06-21 2:43 ` John McCutchan
2005-06-21 15:55 ` Robert Love
2005-07-14 0:25 ` Neil Brown
2005-07-14 4:11 ` John McCutchan
2005-06-18 0:05 ` Arnd Bergmann
2005-06-18 0:57 ` Robert Love
2005-06-18 1:51 ` Chris Wedgwood
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=42B2FBF3.6010607@nortel.com \
--to=cfriesen@nortel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rml@novell.com \
--cc=ttb@tentacle.dhs.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=zab@zabbo.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.