similar to: kqueue errors in maillog

Hello, If anyone would like it I have provided a Dovecot 1.0 test61 port and package for FreeBSD 5.3 here. I made them for my own experimentation but thought they might be interesting to others I suppose. http://www.helenmarks.co.uk/~dom/dovecot/ These deviate from the stock test61 because I've updated and added a patch I wrote a long time ago for ioloop kqueue/kevent support in

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

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

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

I rewrote much of the kqueue code since the old code didn't handle properly the case when both input and output I/O handlers were added to the same file descriptor with different callbacks. This is done commonly in Dovecot, so I'm wondering why more people didn't complain about problems with it.. :) I don't anyway have access to any BSDs so the code is completely untested. Please

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, 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

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

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

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

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 =" > >>> >

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

> 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 folks - I am configuring a new system and the antispam plugin is the last piece I need, everything else is working. Thanks to Johannes for this plugin, it's exactly what I want and an elegant solution for filter training. But I've been trying everything I can think of for the last 3 days to get this to work, no success. I've got: Postfix 2.5.3, dspam 3.8.0, Dovecot 1.1.6,

Hi Junaid, Sorry about the confusion, indeed I gave you the wrong output. So let's start to the beginning. I disabled quota and I reactivated it My configuration : Volume Name: venus Type: Distributed-Replicate Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: ylal3020:/soft/venus Brick2: ylal3030:/soft/venus Brick3: yval1000:/soft/venus Brick4:

Hi, I am looking to decompile x86 ASM to LLVM IR. The original C is this: int test61 ( unsigned value ) { int ret; if (value < 1) ret = 0x40; else ret = 0x61; return ret; } It compiles with GCC -O2 to (rather cleverly removing any branches): 0000000000000000 <test61>: 0: 83 ff 01 cmp $0x1,%edi 3:

James Courtier-Dutton <james.dutton at gmail.com> writes: > I am looking to decompile x86 ASM to LLVM IR. > The original C is this: > int test61 ( unsigned value ) { > int ret; > if (value < 1) > ret = 0x40; > else > ret = 0x61; > return ret; > } > > It compiles with GCC -O2 to (rather

My NFS server is on 192.168.10.10, with the following setup in /etc/exports: /backup 192.168.10.0/24(rw) Then, form a client (192.168.10.11), I run mount 192.168.10.10:/backup /bck, but get the following error: root at vps01 [~]# mount 192.168.10.10:/backup /bck mount.nfs: Input/output error On the main server, I see this in /var/log/messages: Mar 8 08:42:52 venus kernel: kjournald starting.