[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 4 Apr 2014 22:24:02 +0200
From: Stef Bon <stefbon@...il.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: mtk.manpages@...il.com, John McCutchan <john@...nmccutchan.com>,
Robert Love <rlove@...ve.org>, Eric Paris <eparis@...hat.com>,
Lennart Poettering <lennart@...ttering.net>,
radu.voicilas@...il.com, daniel@...llard.com,
Christoph Hellwig <hch@...radead.org>,
Vegard Nossum <vegard.nossum@...cle.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
linux-man <linux-man@...r.kernel.org>, gamin-list@...me.org,
lkml <linux-kernel@...r.kernel.org>,
inotify-tools-general@...ts.sourceforge.net
Subject: Re: Things I wish I'd known about Inotify
2014-04-03 17:38 GMT+02:00 Eric W. Biederman <ebiederm@...ssion.com>:
>
> Other pitfalls.
>
> Inotify only report events that a user space program triggers through
> the filesystem API. Which means inotify is limited for remote
> filesystems
I'm working on enabling fsnotify for fuse. The sending of a watch/mask
to userspace works, and the fuse filesystem can forward the watch to
it's backend.
Reporting delete events back to the kernel works with the help of one
existing call fuse_lowlevel_notify_delete. There is no existing call
to report a create, so I'm working on that.
( at this moment I'm trying to enable the most simple events : delete
and create of an entry in a directory which is watched).
Stef Bon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists