Kees Bakker wrote: > Solved. See below.
> Anyway, thanks Ángel for the suggestion to use the command that way. It's always useful to remove extre layers when debugging :) > Does that mean that my configuration was incorrectly attempting to > use fam, when gamin was installed? Does courier-imap do this discovery > automatically? If so, it made the wrong choice. > Yes, it was attempting to use fam but failing. When watching a maildir courier-imap gives 15 seconds for connecting with fam (maildir/maildirwatch.c: maildirwatch_alloc). This was added in 4.8.1: > * maildir/maildirwatch.c (maildirwatch_alloc): Use alarm() to kill > the process if FAMOpen() takes more than 15 seconds to return. > Should prevent a hung process if FAM/Gamin is fubared. Seems that a signal(SIGALRM, SIG_IGN); would have been a appropiate. If FAMOpen failed with EINTR, courier would have been able to continue without dying. Although in this case, the problem was that fam was completely unusable, not that it occasionally freezed. I suspect you had a /tmp/fam-vmail- abstract socket (maybe once upon a time it was installed), but fam wasn't running (not even installed, from your log). I'm glad you fixed your issue. Best regards ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
