similar to: new inotify patch

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 ..... :

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

Hi, So I was testing things with inotify notifications enabled and noticed that when I a) select a mailbox other than the inbox b) IDLE c) copy mail into the /new folder in that mailbox nothing happens! So I straced it and it always opens the inbox's new/ and cur/ directories for notifications. Is that the correct behaviour? I assumed that if I select some mailbox other than the inbox, IDLE

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

Hi, I've come across some possibly buggy behaviour with regards to Dovecot and the use of the IDLE keyword. Found this while testing out inotify support for Johannes - although after asking him and him reproducing it, he is of the opinion that it's not a inotify specific problem. The behaviour is that when the client is idling, Dovecot seems to only alert to the first new message

https://bugzilla.samba.org/show_bug.cgi?id=14262 Bug ID: 14262 Summary: add continuous sync mode using inotify/fanotify/etc Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayne at opencoder.net

I'm seeing this message in my /var/log/maillog: May 26 12:35:00 agencymail dovecot: IMAP(info at example.com): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances I rummaged through google, and found : http://www.dovecot.org/list/dovecot-cvs/2008-May/011132.html which says I need to increase /proc/sys/fs/inotify/max_user_instances (no

Hi, I looked through the web and the list archives, but couldn't find how to set up the following: - dovecot with ssl/tls enabled - login from localhost allowed with and without tls - login from remote hosts only allowed via tls Is that possible at all? I'm using debian/unstable so its version 0.99.10.4-3. Thanks, johannes -- http://www.sipsolutions.de/ Key-ID: 9AB78CA5 Johannes

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:

Sparked from the discussion on the list, I've put my antispam plugin into git and split up the code into a frontend and possibly multiple backends. See http://git.sipsolutions.net/dovecot-antispam.git/ (URL functions as both gitweb and git URL) Andreas, I took your README file and adjusted it, I hope you don't mind. I didn't fork from your git tree because you'd already

Please forgive me if direct email is not appropriate, but I am at my wit's end. I am running Kernel 2.6.35.2. Previously, I was running 2.6.32.something (don't know at this point). Samba is 3.4.8-59. I have been getting the inotify errors on both the old and the new Kernel, to the point that it filled my hard drive and made my Windows/XP unrecoverable. It appears to only happen

http://dovecot.org/ It's hot in here. Something like 25-30c for many days now. My brains don't work in that heat. So, this is still not an 1.0-alpha1. I'll put it out when I think the release will actually be fully working :) Changes since test76: - Fixes to FETCHing MIME body parts, especially with message/rfc822 attachments. We hadn't been handling this entirely correctly

https://bugs.freedesktop.org/show_bug.cgi?id=29934 Summary: X locks up when hotplugging second monitor Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hey, Sorry for dropping in like this, couldn't find any information on this and I guess I'm too lazy to read all the relevant bits and pieces of the kernel sources to find out: I'm currently running encrypted root and swap, but would still like to use suspend to disk. Would early userspace be capable of inserting the crypto-loop module into the kernel, load the keys off my

https://bugs.freedesktop.org/show_bug.cgi?id=29935 Summary: X locks up with second monitor with DPMS Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

On 4/19/06, Johannes Berg <johannes at sipsolutions.net> wrote: > On Tue, 2006-04-18 at 22:56 +0200, Marcus Rueckert wrote: > > > libdspam instead of system("dspam...") > > That's a lot of work, how about calling to the dspam server instead? I'm about to start building a system for ~10,000 users, using dovecot, and was going to use dspam with it... Is

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

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'm going through my messages log and I've noticed a large amount of the following error going on. What affect would this have on the smb client that is connected to those pid's? Mar 11 11:35:24 process1 smbd[25349]: [2010/03/11 11:35:24, 0] smbd/notify_inotify.c:293(inotify_setup) Mar 11 11:35:24 process1 smbd[25349]: Failed to init inotify - Too many open files

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