On 20.4.2007, at 18.36, Erich Schubert wrote:
Hi,Do the logs contain something interesting? Could you please strace dovecot's imapd and send here the resulting trace after the crash?It's not totally reproduceable. But I found something interesting in the logs: Apr 20 16:32:06 [dovecot] Time just moved backwards by 8 seconds. This might cause a lot of problems, so I'll just kill myself now.
Apparently your laptop's clock is running too fast and then unsuspension script(?) sets the time to be correct, and ends up moves the it backwards. Dovecot really doesn't like that, and I'm not sure if there's any reasonable way that Dovecot can handle that. In general it's not meant to be run in laptops.. The best solution would be if the time was set correct before Dovecot had a chance to run at all, but that'll probably require either kernel changes or changing the way unsuspension handles time. Or maybe it's ntpd instead of unsuspension that notices time has moved too much.
Another possibility would be to just increase Dovecot's "allowed sleep time before killing itself". By default that's 5 seconds.
PGP.sig
Description: This is a digitally signed message part
