Re: [systemd-devel] Suggestion for a lowlevel fsnotify change daemon.

2015-07-28 Thread Stef Bon
2015-07-28 19:20 GMT+02:00 Simon McVittie : > On 28/07/15 17:28, Mantas Mikulėnas wrote: > > At first look, this seems very similar to FAM (which even supported > > NFSv3, using custom notifications over SunRPC). > > > > Later I remember GNOME replaced it with Gamin and finally with > > local-only

Re: [systemd-devel] Suggestion for a lowlevel fsnotify change daemon.

2015-07-28 Thread Simon McVittie
On 28/07/15 17:28, Mantas Mikulėnas wrote: > At first look, this seems very similar to FAM (which even supported > NFSv3, using custom notifications over SunRPC). > > Later I remember GNOME replaced it with Gamin and finally with > local-only inotify inside glib/gvfs. What GLib actually uses is a

Re: [systemd-devel] Suggestion for a lowlevel fsnotify change daemon.

2015-07-28 Thread Mantas Mikulėnas
At first look, this seems very similar to FAM (which even supported NFSv3, using custom notifications over SunRPC). Later I remember GNOME replaced it with Gamin and finally with local-only inotify inside glib/gvfs. It might be useful to revive it, both inotify and fanotify have problems. But I g

[systemd-devel] Suggestion for a lowlevel fsnotify change daemon.

2015-07-28 Thread Stef Bon
Hi all, for some time I have been looking at the issue why fsnotify does not work with network filesystems and FUSE (with a shared backend). I've found out that changes initiated on the localhost, on the filesystem are supported by the fs change subsystems on Linux, and events initiated at the ba