dovecot-imapd incompatible with ntpdate use
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dovecot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: dovecot-imapd
As described at http://
Possible fixes:
1. Add an "ntp" dependency to the dovecot-imapd package, so that ntpdate invocation won't be so likely to trigger a clock reset backwards and imapd failure. For extra points (if this isn't the case already) have the if-up.d/ntpdate script abort if ntpd is running.
- or -
2. Alter the if-up.d/ntpdate script so it does _not_ run ntpdate just if dovecot-imapd is running.
- or -
3. Patch dovecot-imapd so that when it aborts for this reason it puts a notice on all open tty's - since asking sysadmins to watch the logs for its shutdown notice when doing the seemingly unrelated task of bringing up an interface is a bit much.
- or -
4. Make all 3 changes.
(This is on an Intrepid system that the behavior was noticed. But if-up.d/ntpdate has been there for awhile - certainly it's in Hardy - with dovecot-imapd 1:1.1.4-
I just reproduced this exact issue in Jaunty (dovecot 1:1.1.11-0ubuntu2). That is; I set my clock to run ahead, restarted my network which triggered a ntpdate. Hence my clock was set back to the correct time, leading to dovecot shutting itself down.
"dovecot: Fatal: Time just moved backwards by 420 seconds. This might cause a lot of problems, so I'll just kill myself now. http:// wiki.dovecot. org/TimeMovedBa ckwards"
Today dovecot-common Suggest the package ntp. Perhaps it could at least be upgraded to a Recommends?