On Mon, Mar 31, 2014 at 1:00 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
>
> ... 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...
None of that matters.
A good file manager uses fsnotify to get efficient and timely local
notifications, and also does polling to check by hand - much less
timely, but covers the remote case.
The point is, fsnotify is very much a valid thing to do even on
networked filesystems, and even if you don't get full coverage.
The fact that people then *also* may use it incorrectly and think that
it is sufficient *without* the polling, that's not our problem. The
fact that stupid uses exist is not a reason to disable something that
_can_ be used intelligently.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
