Roy Marples uberlord@gentoo.org writes:
So I've hacked up a patch to dovecots configure.in that only enables inotify if it really works :) It also tests for inotify, then kqueue, then dnotify if no notify method is specified. Seems to work well.
If upstream (Timo) accepts it then I'll roll it into beta9's ebuild ASAP
A better solution would be to have something in the code though as if the kernel suddenly drops to <2.6.13 then you'll get the same errors.
In the meantime, I've forced the beta9 ebuild to only use inotify if
=glibc-2.4 and >=linux-headers-2.6.16 are present, and I hope glibc has been compiled against them - lol.
So was that supposed to prevent that error?
Is this log output from the same problem:
dovecot: Jun 27 13:07:52 Error: pop3-login: inotify_init() failed: Function not implemented
dovecot: Jun 27 13:07:57 Info: pop3-login: Disconnected: rip=192.168.0.16, lip=192.168.0.4
dovecot: Jun 27 13:07:57 Error: pop3-login: inotify_init() failed: Function not implemented
dovecot: Jun 27 13:08:02 Info: pop3-login: Disconnected: rip=192.168.0.16, lip=192.168.0.4
dovecot: Jun 27 13:08:03 Error: pop3-login: inotify_init() failed: Function not implemented