similar to: BSD people, please test kqueue changes

Hi, I would like to submit the attached patch. It implements IO loop using FreeBSD's kqueue/kevent syscalls. It is based on snapshot of CVS HEAD as of 2005-12-12. I could only give it limited testing on FreeBSD 5.4 but it works fine so far. Vaclav Haisman -------------- next part -------------- diff -rN -u old-dovecot-cvs/autogen.sh new-dovecot-cvs/autogen.sh ---

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

Hello, attached patch adds experimental ioloop handler which uses BSD kqueue API. It compiles and survives my small test program, but not thoroughly tested because I have no suitable BSD machine to torture. Brave owners of (Free|Net|Open)BSD please test and report results :) Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net

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

On 16-07-03 03:30:36, Timo Sirainen wrote: > On 02 Jul 2016, at 03:30, Adam Weinberger <adamw at adamw.org> wrote: > > > >>> Jul 1 10:07:27 imap dovecot: master: Panic: kevent(EV_ADD, READ, 54) failed: Bad file descriptor > >>> > >>> It's not dumping core, and I get the message even with "protocols =" > >>> >

> On 1 Jul, 2016, at 10:52, Timo Sirainen <tss at iki.fi> wrote: > > On 01 Jul 2016, at 19:39, Adam Weinberger <adamw at adamw.org> wrote: >> >> Hi, >> >> 2.2.25 crashes on FreeBSD with a kqueue-related message. I see references to something similar (http://www.dovecot.org/list/dovecot/2012-February.txt) from a couple years ago. >> >> I

Hi, 2.2.25 crashes on FreeBSD with a kqueue-related message. I see references to something similar (http://www.dovecot.org/list/dovecot/2012-February.txt) from a couple years ago. I get: Jul 1 10:07:27 imap dovecot: master: Panic: kevent(EV_ADD, READ, 54) failed: Bad file descriptor It's not dumping core, and I get the message even with "protocols =" Downgrading back to 2.2.24

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

Apparently Dovecot with kqueue ioloop enabled causes random crashes in FreeBSD 9.1. Anyone else noticed something like that? I'm wondering if Dovecot's kqueue code has a bug somewhere (I can't find it) or could it be that FreeBSD itself has a bug? Anyway it seems to be returning events for filters that have already been removed.

Hi, We have a issue with a server pretty much just running dovecot, there's about 250gb of maildirs which has about 200 simultaneous connections to it running on freebsd 7. The machine has stayed up for about 8 days before it panics but sometimes panics after about 24 hours. We are running a PAE kernel (with ULE scheduler) as the machine has 2 (4 core processors) and 8gb of ram, dovecot is

Was running dovecot-1.0.rc2 but many stale imap processes (only one user of IMAP). Switched to dovecot-1.0.rc6 but problem continued. This is on FreeBSD 4 something. Maybe it has bug with kqueue?? I read messages about the stale imap processes on the list. It seems to hit *BSD systems. But email about new release candidate indicated it should be fixed. I read on the pkgsrc commit list

So, apparently the original kqueue code was working fine after all, although it was much more complex than it really needed to be. So, this time there's a really simple and pretty kqueue implementation: http://dovecot.org/nightly/dovecot-latest.tar.gz Tested that it seems to work with FreeBSD. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc

Hi, The sample program given below freezes my 5.1R installation. This program is from a bug report - kern/54331. That bug report (http://lists.freebsd.org/pipermail/freebsd-bugs/2003-July/001608.html) is for the shutdown function call, whereas my machine basically just freezes up and reboots on kevent itself. I am also noticing this problem with another program i wrote (but too long to include

I've been using the macports version of dovecot, which is 1.1.11, on MacOS 10.5.6 $ /opt/local/sbin/dovecot --exec-mail imap Fatal: kevent(EV_ADD, 0) failed: Operation not supported This version is configured --with-ioloop=kqueue The problem seems to be known, if not understood: http://lists.apple.com/archives/Darwin-userlevel/2008/Dec/msg00010.html However, if I use

Hi to ALL! I have dovecot-1.0r7 installed on FreeBSD 6.1, using kqueue and Maildir (<20 mailboxes, < 0,5 Gb size). Periodically CPU load of imap processes increasing up to 60-80%. Is it normall behavior or not? May be somebody had such kind of problems? -- ? ?????????, ?????? ????? ??? "???????" : ?????????? ??, WEB-?????????? +7 (495) 589 68 81 +7 (926) 575 22 11

I built and install Dovecot 2.0Beta4 on my NetBSD/amd64-current system, and am seeing the user-owned imap processes busy-looping. In Dovecot 1.2.x (and 1.x and 0.x..) I force ionotify and ioloop to kqueue, so I suspected that was the problem. Turns out it's not: Using poll or none also causes the same problem. This did not happen in 1.2.8 (didn't try anything later than that).

The attached patch should fix the problem with dying imap on "Unrecognized event". The problem is that when we register a handle for IO_ERROR only, we still can get readable/writable event without EV_EOF being set. This case was not handled. -- Vaclav Haisman -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: io-kq.diff URL:

A few weeks back I upgraded my mail server to -STABLE from a 4.2-STABLE incarnation that had been running for years. Part of recompiling everything on the box involved disassociating my use of the sendmail port I was using and to use the base sendmail in -STABLE. -STABLE builds with libmilter, so I simply recompiled one of my milter clients with the milter headers, objs, etc that were produced

dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- kqueue.c: line 66 (event_callback): assertion failed: (io->refcount == 1) dovecot: Nov 24 12:49:06 Error: IMAP(user): Raw backtrace: 2 imap 0x0000000100068e82 default_fatal_finish + 41 -> 3 imap 0x0000000100068eed i_syslog_fatal_handler + 0 -> 4 imap 0x0000000100068687 i_info + 0 -> 5 imap

http://dovecot.org/releases/dovecot-1.0.rc7.tar.gz http://dovecot.org/releases/dovecot-1.0.rc7.tar.gz.sig Can everyone now agree that there are no more hangs? :) * Require that Dovecot master process's version number matches the child process's, unless version_ignore=yes. Usually it's an accidental installation problem if the version numbers don't match. * Maildir: Create