Date: Wed, 08 Feb 2006 14:28:56 -0600 From: eculp@encontacto.net To: Alex Dupre <ale@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: gamin 0.1.7 Message-ID: <20060208142856.0ojbnsgmmw0c80o0@mail.encontacto.net> In-Reply-To: <43EA4F1F.8060206@FreeBSD.org> References: <43E9FFAE.5020500@FreeBSD.org> <20060208133916.dzyx74skookookk4@mail.encontacto.net> <43EA4F1F.8060206@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Alex Dupre <ale@FreeBSD.org>: > eculp@encontacto.net wrote: >> I'm a bit confused. With this port will the fam/gamin conflict with >> courier still exist or will gamin be used in place of fam? > > gamin is a replacement for fam. Unfortunately it's not 100% > compatible with fam. suspend/resume monitor is not implemented for > security reasons, but the main *undocumented* difference is the use > of the select(2) system call to check if there are new events to be > read. For different reasons it may be that select() doesn't find any > new events, while FAMPending find them, and viceversa. The only safe > and correct way to check for pending events before calling a > non-blocking FAMNextEvent is to call FAMPending before and after the > select() system call (and return true as soon as any call to > FAMPending return true). > I don't know why courier-imap doesn't work with gamin. If the problem > was a bug in gamin, maybe I've fixed it, but if it was due to one of > the differences exposed above then the problem remains unless we fix > the courier code to work with gamin. Alex, IIRC, gamin was dumping core, but since it was a production server I didn't look further but went back to courier. I hope someone else had time to look at it a bit closer. If you think the new version has a chance of working with courier, I could give it a try. Early tomorrow morning or maybe this evening if I can get caught up. (CST). ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060208142856.0ojbnsgmmw0c80o0>