similar to: RSYNC + iNotify

Greetings, I just have a couple of questions. One is related to Samba specifically the second deals with Windows Networking, RSYNC, and Linux in general. I have asked it in the RSYNC mailing list, but so far no one has provided any insight. I apologize if anyone has gone over this information. I have been unable to find much help in the mailing list archives, IRC, or the documentation.

I am experiencing an odd problem while attempting to mount and access a directory with smbfs. smbclient does not exhibit the same behavior. I have created a directory /mnt/smb-test and am attempting to mount a volume from a NetApp Filer running OnTap 7 with NTFS security mode. An Active Directory DC handles security for the share. The Linux machine shows as registered in AD and I can use

Hi, dovecot (1.0.alpha5) won't compile with inotify support because inotify.h can't be found. I'm running Linux 2.6.15-rc5 with headers from 2.6.12 (like most vendors). I've noticed that beagle and other inotify-enabled applications ships with an inotify.h. Could this be scheduled for alpha6? :-)

hi, the current code has changed include linux/inotify.h to sys/inotify.h since 2006-01-17, but that won't work with inotify*.h as documented in the wiki. One has to either revert back to linux/inotify.h, or add #include <sys/inotify-syscalls.h> to both configure.in and src/lib/ioloop-notify-inotify.c Or, just symlink sys/inotify.h -> linux/inotify.h. That's on Debian 3.1

On Wed, Sep 17, 2008 at 12:32:40PM +0300, Kirill A. Shutemov wrote: > On Tue, Sep 16, 2008 at 07:09:02PM +0300, Adrian Bunk wrote: > > On Tue, Sep 16, 2008 at 07:10:25AM -0700, Ulrich Drepper wrote: > > > Kirill A. Shutemov wrote: > > > >> What is the error message? > > > > > > > > /usr/include/asm-generic/fcntl.h:117: error: redefinition

I've added this to our klibc copy in the udev tree to support the recently added Inotify. Thanks, Kay -------------- next part -------------- diff --git a/klibc/klibc/SYSCALLS.def b/klibc/klibc/SYSCALLS.def --- a/klibc/klibc/SYSCALLS.def +++ b/klibc/klibc/SYSCALLS.def @@ -114,6 +114,9 @@ int lchown32,lchown::lchown(const char * int getcwd::__getcwd(char *, size_t) <?> int utime(const

Hi, I note that dovecot supported inotify from -test77, and now the Linux kernel supports it starting from linux-2.6.13-rc3. So in theory I should be set to go. I'm using an -mm kernel, and it was built with inotify, on FC4/devel. However when trying to build with it using --with-notify=inotify, I always seem to be getting this message: checking for poll... yes configure: error:

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

Hi, I'm trying to compile Dovecot beta2 with inotify support, but this is unsuccessfull. First, it seems that the configure script is looking for inotify.h in /usr/include/sys, whereas it is in /usr/include/linux on my Debian Sarge system. But that's a minor point, let's make a symlink. % dpkg -S /usr/include/linux/inotify.h linux-kernel-headers: /usr/include/linux/inotify.h % dpkg

Hi, I've seen some chatter on NFS boards about kqueue being more reliable than inotify when used in NFSv3 and NFSv2. The chatter is a bit old so I don't know if it is true anymore. Anyone have pro/con experience with dovecot on the inotify/kqueue question when using NFS storage? I realize that kqueue is probably a bit slower and causes some delay with IDLE. Also, it may not really

Hi Reuben, I hope you don't mind me copying the dovecot list again. > dovecot: Aug 21 04:08:22 Error: IMAP(reuben): inotify_rm_watch() failed: > Invalid argument Odd. > This is with a 2.6.13-rc6-mm1 release. I've posted to LKML because there is > also a kernel stack produced at one point which looks inotify related (but the > messages above are contant). > See

Is Inotify **fully supported** by OCFS2? Thank you

Hi, I am compiling dovecot and I found dnotify & inotify. What does dnotify or inotify do ? do i need it. Thanks

(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

Hello, I've a problem on my system with inotify. In the smbd logfile are shown a lot messages like this: [2015/06/10 11:15:21.644453, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup) Failed to init inotify - Too many open files [2015/06/10 11:15:23.968497, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup)

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, I recently switched from courier imap to dovecot. With courier I had a working IDLE setup that informed me immediately when new mail arrived. With Dovecot it is different, sometimes i get an immediate result but most of the time it takes a rather long time for the notification to return to the client. For testing purposes I set mailbox_idle_check_interval = 1 and i now get the same

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

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

>From my log: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances # wc -l subscriptions 95 # cat /proc/sys/fs/inotify/max_user_instances 128 Why does 95 exceed 128? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin