From: Robert Love <rml@novell.com>
To: Rusty Lynch <rusty.lynch@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] inotify for 2.6.11
Date: Tue, 05 Apr 2005 21:21:23 -0400 [thread overview]
Message-ID: <1112750483.13601.10.camel@phantasy.site> (raw)
In-Reply-To: <pan.2005.04.06.00.53.44.705260@intel.com>
On Tue, 2005-04-05 at 17:53 -0700, Rusty Lynch wrote:
> From just a casual look, it seems like this could be used to monitor the
> comings and goings of processes by monitoring /proc. Unfortunately
> inotify doesn't seem to be getting all the events on the proc filesystem
> like it does on a real filesystem because I am not seeing new events every
> time a new process is added or removed. The same is true if you attempt
> to monitor something like /sys/bus/usb/devices/ and add/remove a usb
> device.
>
> On a side note, it's still rather interesting to monitor /proc and watch
> all the traffic.
Yah, I agree. I looked into doing this awhile back, when I noticed
inotify did not generate events for /proc. We just need to add calls to
the fsnotify hooks to the proc_create() and proc_delete_foo() stuff.
The interfaces are capable, e.g. we can add support at anytime, even
after inotify is merged. I'd be for it.
Robert Love
next parent reply other threads:[~2005-04-06 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EqlI-2DI-59@gated-at.bofh.it>
[not found] ` <3PRs6-89U-15@gated-at.bofh.it>
[not found] ` <3PYWC-636-7@gated-at.bofh.it>
[not found] ` <3Q0F6-7Ar-37@gated-at.bofh.it>
[not found] ` <3Q4z0-2tA-15@gated-at.bofh.it>
[not found] ` <pan.2005.04.06.00.53.44.705260@intel.com>
2005-04-06 1:21 ` Robert Love [this message]
[not found] <3Q7wT-4HJ-11@gated-at.bofh.it>
[not found] ` <3Q7wT-4HJ-13@gated-at.bofh.it>
[not found] ` <3Q7wT-4HJ-15@gated-at.bofh.it>
[not found] ` <3Q7wT-4HJ-17@gated-at.bofh.it>
[not found] ` <3Q7wT-4HJ-19@gated-at.bofh.it>
[not found] ` <3Q7wT-4HJ-21@gated-at.bofh.it>
[not found] ` <3Q7wT-4HJ-9@gated-at.bofh.it>
[not found] ` <pan.2005.04.08.01.37.42.462474@intel.com>
2005-04-08 1:52 ` Robert Love
2005-03-07 3:13 Albert Cahalan
2005-03-08 1:00 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 18:37 Robert Love
2005-03-04 21:38 ` Timothy R. Chavez
2005-03-04 21:40 ` Robert Love
2005-03-06 0:04 ` Christoph Hellwig
2005-03-06 0:40 ` Robert Love
2005-03-07 1:23 ` Christoph Hellwig
2005-03-07 4:33 ` Robert Love
2005-04-05 7:58 ` Prakash Punnoor
2005-04-05 16:12 ` Robert Love
2005-04-05 17:20 ` Prakash Punnoor
2005-04-05 17:35 ` Robert Love
2005-04-05 22:09 ` Robert Love
2005-04-06 3:21 ` Adam Kropelin
2005-04-10 16:16 ` Erik Meitner
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=1112750483.13601.10.camel@phantasy.site \
--to=rml@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty.lynch@intel.com \
/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
all inboxes | Powered by JetHome®