similar to: IDLE with inotify problem

Hi List! Attached is a patch to configure.in to test that epoll, poll, inotify, kqueue and dnotify actually work. It also attempts to select the best one for you if none specified. This supercedes my previous patch in the re beta9 thread. Hopefully get this in Gentoo's beta9 ebuild soon. Thanks -- Roy Marples <uberlord@gentoo.org> Gentoo/Linux Developer (baselayout, networking)

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

Dear all :) I have been upgraded dovecot today and I get following errors: Jun 14 12:08:54 [dovecot] IMAP(adnae@xxxxxx.xxx): inotify_init() failed: Function not implemented Jun 14 12:08:54 [dovecot] IMAP(auftrag@xxxxxxx.xxx): inotify_init() failed: Function not implemented Jun 14 12:08:54 [dovecot] IMAP(swolf@xxxxxx.xxx): inotify_init() failed: Function not implemented I have a 64 bit

Hi, the attached patch contains these changes: 2005-12-15 22:18 Vaclav Haisman <v.haisman@sh.cvut.cz> * src/lib/ioloop-kqueue.c: Fix IO_ERROR behaviour. * src/lib/ioloop-notify-kqueue.c: New file. * configure.in: Improve kqueue detection and handling. Cleanup. The configure.in changes that are not related to kqueue are there to make autoconf 2.59, automake 1.9.6 and libtool 1.5.20

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

Hello, is my understanding of the parameter "imap_idle_notify_interval" right, if i say, it's the time between two point where dovecot tells the client he is here, and sould have nothing directly todo with the notification of new mails arrived. I played with the values around. And the courios is, in thunderbird the folloing. set to 30 seconds. Thunderbird pop up around 25 seconds

Hi there We have a Samba-based "upload server" where people put files to be processed. Anyway, when they upload files, a Unix-based script runs and moves the files off. However, the Windows explorer app doesn't "notice" the removal, and the user still sees the files. If they F5/refresh explorer, the files indeed have disappeared. If I have two explorer windows open

Ever since Columbus day things have been strange with my two dovecot servers, according to my Blackberry users. We do not have a BES just the standard BIS that comes with a personal account. Several people have told me that since that Monday that they get occasional duplicate copies of messages which only appear singularly in their Maildir inboxes. I myself even called VZW and got

Hi, Is there any plans to use the Linux inotify, which is a major improvement over dnotify ? (Linux mechanism for communicating filesystem events to user space) Regards, -- Nico ?crivez dans l'ivresse, mais relisez-vous ? jeun. -+- Andr? Gide (1869-1951) -+-

Hi, sorry for this question, but I didn't find the information in the documentation or wiki: Is mailbox_idle_check_interval (in dovecot.conf) in seconds or minutes? I think it's minutes. But ... It would be nice, if this will be in the docu of the dovecot.conf. Thanks Rupert

I've been researching the state of 'file alteration monitoring' technology on Linux. Famd uses dnotify to inefficently monitor a handful of directories. The replacement for dnotify is being worked on in the kenel and it's called inotify. If I understand it correctly and they get it finished, it would be an awesome addition to rsync. With it, you could run rsync to update a

Hi, I sometimes got the following log entries with dovecot 1.1.11 : mail.err: Feb 27 10:06:54 dovecot: IMAP(hidden at email.com): write(dnotify pipe) failed: Bad file descriptor mail.err: Feb 27 10:06:54 dovecot: IMAP(hidden at email.com): close(dnotify pipe[0]) failed: Bad file descriptor mail.err: Feb 27 10:06:54 dovecot: IMAP(hidden at email.com): close(dnotify pipe[1]) failed: Bad

Are there any differences with how both IDLE and "UID FETCH n:n+x (FLAGS UID...)" are handled when Dovecot is using a "mail" vs. a "Maildir" user? I have recently implemented support for IDLE (Push E-mail) in a client infrastructure that I'm building. I haven't in depth checked out what the problem might be, but when Dovecot was using the "mail" dir

I got lots of errors that look like this: Error: write(dnotify pipe) failed: Bad file descriptor I am running dovecot-1.2.4-0_99 on RHEL4 dovecot -n: # 1.2.4: /etc/dovecot.conf # OS: Linux 2.6.9-89.0.3.ELsmp x86_64 Red Hat Enterprise Linux AS release 4 (Nahant Update 8) ext3 log_path: /var/log/dovecot info_log_path: /var/log/dovecot-info login_dir: /var/run/dovecot/login

I've run this test on every permutation of poll and notify: can NOT reproduce the crash: --with-ioloop=select --with-notify=none --with-ioloop=select --with-notify=dnotify --with-ioloop=select --with-notify=inotify --with-ioloop=poll --with-notify=none --with-ioloop=poll --with-notify=dnotify --with-ioloop=poll --with-notify=inotify CAN reproduce the crash: --with-ioloop=epoll

Hello, I use Thunderbird as IMAP client and do a lot of server-side filtering with Sieve scripts. To be notified of new mails, I want to check all folders (a lot of them...) at once for new mails, and not only the inbox. According to http://kb.mozillazine.org/Checking_for_new_messages_in_other_folders_-_Thunderbird it should be sufficient to enable one setting -- given that the IMAP server

Hello. About year ago I tested OE and dovecot imap and met this problem (http://wiki.dovecot.org/Clients#head-129bcbfc238b5c34362b8216db87c05e7a34af85) - Using "Headers only" synchronization is buggy and can cause "Message is no longer available on this server" error when opening a mail. I configured OE to sync All messages, and it worked, but then it's acts like pop3 and

Hey, I noticed that there was an ioloop "module" (if we can call it that) for select and poll and decided to add one for kqueue (aka kevent) BSDs high performance descriptor multiplexing API. I haven't done any of the configure glue stuff but the code is complete and works well. kqueue is available on all recent versions of FreeBSD, NetBSD, OpenBSD and Darwin (and therefore MacOS

I''d like to monitor a folder and when someone drops a file in there I can take the files name and add it to a database. My dream is to have a folder always being watched. and if someone drops a file or folders with files into that watched folder, I take the filename(s) and insert them into a db and if the files are in folder I use the folder name(s) as tags for that file. make sense?

Hi, attached patch against test76 adds inotify support and the --with-notify=... configure option that defaults to the current check for dnotify using no special method if dnotify cannot be compiled, and can be set to none, dnotify and inotify. If it is set to dnotify or inotify, failure to compile a test program results in an error. Also, it adds | file change notification method ..... :