All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Does inotify work with special files such as /proc/<pid>/task/<tid>/children?
Date: Sun, 28 Sep 2014 19:44:07 -0500	[thread overview]
Message-ID: <20140928194407.3a584b78@as> (raw)
In-Reply-To: <20140928231240.GC7996@ZenIV.linux.org.uk>

On Mon, 29 Sep 2014 00:12:40 +0100
Al Viro <viro@ZenIV.linux.org.uk> wrote:

> On Sun, Sep 28, 2014 at 11:09:50PM +0000, Steven Stewart-Gallus wrote:
> > Hello,
> > 
> > I can't seem to get inotify to work with special files such as
> > /proc/<pid>/task/<tid>/children? I just need to get a simple yes/no
> > answer on whether it works for special files or whether I have to try
> > a different approach.
> 
> Simple answer: No.  Slightly more expanded one: No, and it won't.
> Inotify does not work on procfs, sysfs, etc.  Doesn't work on
> network filesystems either.  Don't use it.  It was a mistake in the
> first place.

Why was inotify a mistake? Was it badly implemented, or is the whole
concept of userspace being able to monitor filesystem changes
basically impossible to do correctly?

      reply	other threads:[~2014-09-29  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28 23:09 Does inotify work with special files such as /proc/<pid>/task/<tid>/children? Steven Stewart-Gallus
2014-09-28 23:12 ` Al Viro
2014-09-29  0:44   ` Chuck Ebbert [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=20140928194407.3a584b78@as \
    --to=cebbert.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstewartgallus00@mylangara.bc.ca \
    --cc=viro@ZenIV.linux.org.uk \
    /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.