From: Al Viro <viro@ftp.linux.org.uk>
To: "C. Scott Ananian" <cscott@laptop.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: inotify and /proc?
Date: Sat, 23 Jun 2007 00:28:51 +0100 [thread overview]
Message-ID: <20070622232851.GW21478@ftp.linux.org.uk> (raw)
In-Reply-To: <c6d9bea0706221551g2a50e5a1u56a11b1965fdd61d@mail.gmail.com>
On Fri, Jun 22, 2007 at 06:51:10PM -0400, C. Scott Ananian wrote:
> No, clearly inotify on all files in /proc is not the right thing to
> do. But I'm writing support for "RDNSS in RA" -- IPv6 Router
> Advertisement messages can include a DNS server specification, which
> makes IPv6 completely autoconfiguring.
Why the hell do you need idiotify on it? Just make poll(2) work and
be done with that; see e.g. how /proc/<pid>/mounts does it.
next prev parent reply other threads:[~2007-06-22 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 19:54 C. Scott Ananian
2007-06-21 23:17 ` Arnd Bergmann
2007-06-22 22:51 ` C. Scott Ananian
2007-06-22 23:28 ` Al Viro [this message]
2007-06-25 3:12 ` Kyle Moffett
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=20070622232851.GW21478@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=arnd@arndb.de \
--cc=cscott@laptop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome