similar to: inotify and filesystem monitors

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 > developed against libgfapi you could do it (I think). > > On May 3, 2018 9:28:43 AM

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, lemonnierk at 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 least in replica volumes >(disperse probably wouldn't, you wouldn't get

hi guys will we have gluster with inotify? some point / never? thanks, L.

On 01/05/18 23:59, Vijay Bellur wrote: > > > On Tue, May 1, 2018 at 5:46 AM, lejeczek > <peljasz at yahoo.co.uk <mailto:peljasz at yahoo.co.uk>> wrote: > > hi guys > > I have a simple case of: > $ setfacl -b > not working! > I copy a folder outside of autofs mounted gluster vol, > to a regular fs and removing acl works as

I thought this can be useful to someone, so here it goes. I am using automatic SysVol replication with the help of "watcher", a recursive incron. https://github.com/splitbrain/Watcher "Watcher is a daemon that watches specified files/folders for changes and fires commands in response to those changes. It is similar to incron, however, configuration uses a simpler to read ini

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 your clients, not ideal, but that should work. I agree that adding support for inotify

hi guys I have a simple case of: $ setfacl -b not working! I copy a folder outside of autofs mounted gluster vol, to a regular fs and removing acl works as expected. Inside mounted gluster vol I seem to be able to modify/remove ACLs for users, groups and masks but that one simple, important thing does not work. It is also not the case of default ACLs being enforced from the parent, for I

On Tue, May 1, 2018 at 5:46 AM, lejeczek <peljasz at yahoo.co.uk> wrote: > hi guys > > I have a simple case of: > $ setfacl -b > not working! > I copy a folder outside of autofs mounted gluster vol, to a regular fs and > removing acl works as expected. > Inside mounted gluster vol I seem to be able to modify/remove ACLs for > users, groups and masks but that one

Hello world, so, with beta2 of Dovecot 2.0 being available, what is the preferred way to achieve load balancing and fault tolerance? As far as I can see it, there are basically two options: 1) Use a HA shared storage, export either a cluster filesystem or NFS, and have your dovecot servers mount that file system. Load balance these servers (Cisco ACE, ldirectord, ...) and there you go. Overall

lol 60++ posts. 2016-09-29 18:30 GMT-03:00 Miguel Medalha via samba <samba at lists.samba.org>: > >> Problem is -- inotify is not recursive by default. > > Yup. That's why I've been using Watcher, a recursive incron type daemon > written in Python. > > https://github.com/splitbrain/Watcher > -- > To unsubscribe from this list go to the following URL

On Thu, 19 Jul 2018 11:46:43 +0100 lejeczek via samba <samba at lists.samba.org> wrote: > On 19/07/18 10:58, Rowland Penny via samba wrote: > > On Thu, 19 Jul 2018 10:32:04 +0100 > > lejeczek via samba <samba at lists.samba.org> wrote: > > > >> hi guys > >> > >> my samba share has > >> > >> inherit acls = Yes >

On 19/07/18 10:58, Rowland Penny via samba wrote: > On Thu, 19 Jul 2018 10:32:04 +0100 > lejeczek via samba <samba at lists.samba.org> wrote: > >> hi guys >> >> my samba share has >> >> inherit acls = Yes >> >> and inherits(I guess) from global: >> >> create mask = 0744 >> directory mask = 0755 >> >> Now,

I recently moved my backend storage to GlusterFS V3.0 and with one exception everything is running great. That exception is that I had a daemon using inotify that was watching my storage for new files. Upon arrival this watcher uploaded a copy of the file to Amazon S3. This daemon had been running just fine for well over a year. Moving to GlusterFS seems to indicate that inotify doesn't

Just re-tried this, and it doesn't seem to fire getmail on access for me. My incrontab is as follows: /home/user/Maildir/cur/ IN_ALL_EVENTS,IN_ONESHOT /home/user/bin/mvmail.sh The incrontab rule does work, but only if I make a physical change in /home/user/Maildir/cur/ e.g. by moving a mail from another folder in there. Just accessing the particular inbox doesn't seem to trigger

On 19/07/18 12:17, Rowland Penny via samba wrote: > On Thu, 19 Jul 2018 11:46:43 +0100 > lejeczek via samba <samba at lists.samba.org> wrote: > >> On 19/07/18 10:58, Rowland Penny via samba wrote: >>> On Thu, 19 Jul 2018 10:32:04 +0100 >>> lejeczek via samba <samba at lists.samba.org> wrote: >>> >>>> hi guys >>>>

(dovecot v1.2.16) I've notice the log notices about increasing /proc/sys/fs/inotify/max_user_instances on my servers, and started wondering if inotify works for network/cluster filesystems.. I found this: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=311194 which says that there's no mechanism for one node to tell another node that a directory changed for GPFS.. And I

On Thu, 9 Feb 2017 14:43:57 +0100 Axel Kittenberger <axkibe at gmail.com> wrote: > > > > Not only that, but inotify is not guaranteed. (At least not on > > 3.16.0. Can't say regards later versions.) So you might miss some > > changes. > > > > Got any info on that? > > I noted that MOVE_FROM and MOVE_TO events are not guaranted to arrive

.. is this default/desired behaviour? And is this configurable/controllable behaviour? I'm thinking - it would be nice not to have whole vol go read-only(three peers in cluster) but at the same time have gluster alert/highlight the problem to a user/admin. ver. 3.10.3 thanks. L.

Thank you for the acknowledgement. On Mon, Sep 4, 2017 at 6:39 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > yes, I see things got lost in transit, I said before: > > I did from first time and now not rejected. > now I'm restarting fourth(newly added) peer's glusterd > and.. it seems to work. <- HERE! (even though.... > > and then I asked: >

Logs from newly added node helped me in RCA of the issue. Info file on node 10.5.6.17 consist of an additional property "tier-enabled" which is not present in info file from other 3 nodes, hence when gluster peer probe call is made, in order to maintain consistency across the cluster cksum is compared. In this case as both files are different leading to different cksum, causing state in