The gluster client is a userspace application that connects to the
servers and then provides the filesystem interface to the kernel using
the fuse module. The kernel then provides a mountable filesystem.
inotify is a kernel function that watches an inode for changes. That
function would
how about gluste's own client(s)?
You mount volume (locally to the server) via autofs/fstab
and watch for inotify on that mountpoing(or path inside it).
That is something I expected was out-of-box.
On 03/05/18 17:44, Joe Julian wrote:
There is the ability to notify the client already. If you
I do not see it works, simple(st) test I thought would be
local mount points, I do not see fuse/gluster mentions any
options or some elaborate way to make it works, so on mount
points even for replica volumes I do not see glusterfs sends
inotifies.
On 03/05/18 17:44, Joe Julian wrote:
There
There is the ability to notify the client already. If you developed against
libgfapi you could do it (I think).
On May 3, 2018 9:28:43 AM PDT, lemonni...@ulrar.net wrote:
>Hey,
>
>I thought about it a while back, haven't actually done it but I assume
>using inotify on the brick should work, at
Hey,
I thought about it a while back, haven't actually done it but I assume
using inotify on the brick should work, at least in replica volumes
(disperse probably wouldn't, you wouldn't get all events or you'd need
to make sure your inotify runs on every brick). Then from there you
could notify
https://github.com/libfuse/libfuse/wiki/Fsnotify-and-FUSE
On May 3, 2018 8:33:30 AM PDT, lejeczek wrote:
>hi guys
>
>will we have gluster with inotify? some point / never?
>
>thanks, L.
>___
>Gluster-users mailing list
hi guys
will we have gluster with inotify? some point / never?
thanks, L.
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users