Displaying 20 results from an estimated 6000 matches similar to: "inotify support in dovecot"
2006 Jan 23
1
Compiling Dovecot with-notify=inotify
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
2005 Aug 22
2
Re: Dovecot inotify problem
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
2005 Jul 14
1
Changes made to imap descriptor handling in test78?
Hello,
What has changed from test77 to test78 in the way imap manages
its descriptors? I upgraded to test78 this morning on a small
site which I use as a testbed for testing various things.
Running the same copy of my kqueue patch with test77 works
quite well [*], with test78 imap has some problems. Here is
some debugging output I recorded:
Jul 14 12:55:27 egg dovecot: imap-login: Login:
2005 Dec 11
1
inotify.h not found
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? :-)
2005 Aug 18
2
Dovecot IDLE problem (was Re: inotify support in dovecot)
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
2009 May 27
2
Inotify instance limit for user exceeded, disabling?
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
2007 Nov 02
2
*notify config for 1.0.x doesn't enable inotify
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
2008 Sep 17
1
[PATCH] linux/inotify.h: do not include <linux/fcntl.h> in userspace
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
2015 Jun 10
3
Failed to init inotify - Too many open files
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)
2011 Apr 01
1
inotify and network/cluster filesystems
(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
2018 May 22
0
@devel - Why no inotify?
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
2018 May 03
0
@devel - Why no inotify?
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
2007 Aug 12
7
IDLE with inotify problem
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
2018 May 03
3
@devel - Why no inotify?
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
2010 Aug 11
1
1.2: Inotify instance limit for user exceeded, disabling?
>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
2010 Jan 18
1
Inotify instance limit for user exceeded
Hello,
i saw in my log followed messages:
dovecot: 2010-01-18 13:20:54 Warning: IMAP(user1 at domain1.com): Inotify
instance limit for user exceeded, disabling.
dovecot: 2010-01-18 13:21:01 Warning: IMAP(user2 at domain2.com): Inotify
instance limit for user exceeded, disabling.
dovecot: 2010-01-18 13:21:23 Warning: IMAP(user2 at domain2.com: Inotify
instance limit for user exceeded, disabling.
2009 Feb 05
3
NFS - inotify vs kqueue
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
2010 Jan 25
1
GlusterFS and inotify
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
2008 Feb 28
4
dnotify inotify
Hi, I am compiling dovecot and I found dnotify & inotify. What does
dnotify or inotify do ? do i need it.
Thanks
2013 Mar 07
1
Inotify max_user_instances
Maybe I have multiple problems - dunno.
I've started seeing the following log lines:
Mar 7 07:46:22 bubba dovecot: imap(dmiller at amfes.com): Warning: Inotify
instance limit for user 5000 (UID vmail) exceeded, disabling. Increase
/proc/sys/fs/inotify/max_user_instances
max_user_instances is currently 128.
I've tried stopping and restarting dovecot - the message immediately
returns.