From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Quentin Glidic <sardemff7+linux@sardemff7.net>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: inotify/sysfs
Date: Mon, 31 Mar 2014 21:00:19 +0100 [thread overview]
Message-ID: <20140331200019.GQ18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFzXN=fjuFj9wrrO5sUmMTjDFA-uSNqy9ND+Ohfaqdmo9Q@mail.gmail.com>
On Mon, Mar 31, 2014 at 12:13:10PM -0700, Linus Torvalds wrote:
> On Mon, Mar 31, 2014 at 11:52 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > Linus, what do you think about flat-out refusing to create the watches on
> > filesystems that can't support them?
>
> Well, you seem to think that NFS and other network filesystems can't
> support them.
>
> But they can. It's just that they'll only trigger on *local* changes,
> not on remote changes. But if you're doing a file manager on a
> workstation, triggering on local changes is generally exactly what you
> want.
... except when that workstation has e.g. /var/spool/mail NFS-mounted, with
MTA running on server. Or "wait until the job on server puts its results
into this file". And yes, I've seen requests along those lines ;-/
Cluster filesystems have the same issue...
next prev parent reply other threads:[~2014-03-31 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 13:50 inotify/sysfs Quentin Glidic
2014-03-28 17:07 ` inotify/sysfs Jan Kara
2014-03-29 6:25 ` inotify/sysfs Greg KH
2014-03-31 18:52 ` inotify/sysfs Al Viro
2014-03-31 19:13 ` inotify/sysfs Linus Torvalds
2014-03-31 20:00 ` Al Viro [this message]
2014-03-31 20:10 ` inotify/sysfs Linus Torvalds
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=20140331200019.GQ18016@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=sardemff7+linux@sardemff7.net \
--cc=torvalds@linux-foundation.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.