On Jan 8, 2009, at 4:20 AM, Roger Lynn wrote:
On Wed, Jan 07, 2009 at 08:04:25AM +0100, Fabio Tranchitella wrote:
Are you running ntp on your server? You should, it would prevent
your clock
to be moved backwards by 81 seconds all together, and would
probably fix
this behaviour.
I also have a problem with this, caused by running ntp. My server was
switched off for two weeks over Christmas. When it was powered back
on,
ntpd started, immediately followed by Dovecot. 7 seconds later ntpd
reset the time backwards by 26 seconds and Dovecot killed itself,
leaving me to later wonder why mail wasn't working.
Shouldn't the boot process run ntpdate before starting ntpd or other
processes so this wouldn't happen? I know some OSes/distros do this.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
