On 11/05/07, Timo Sirainen [EMAIL PROTECTED] wrote:
On Wed, 2007-05-02 at 10:52 +0200, Amon Ott wrote:
Now I wonder if Dovecot could return errors to the users instead of
dying until time is fine again, e.g. System time has moved
backwards, please come back in n seconds. If the time skip is
On Wed, 2007-05-02 at 10:52 +0200, Amon Ott wrote:
Now I wonder if Dovecot could return errors to the users instead of
dying until time is fine again, e.g. System time has moved
backwards, please come back in n seconds. If the time skip is just a
few seconds, it can of course delay and
Ben Winslow wrote:
Clock drift of about 13 seconds/day (150 PPM) is (unfortunately) not
uncommon, and 4-6 seconds/day (50-75 PPM) is about the norm for PC
hardware in my experience.
Of course, this is exactly the reason why you should run ntpd instead
of ntpdate on a cron job (especially a
On Fri, 11 May 2007 14:50:54 +0300
Timo Sirainen [EMAIL PROTECTED] wrote:
The code already allows the clock to move backwards by 5 seconds
without dying, so how horrible are the clocks in those computers? :)
Clock drift of about 13 seconds/day (150 PPM) is (unfortunately) not
uncommon, and 4-6
Hello Amon,
Amon Ott, 02.05.2007 (d.m.y):
All our systems run ntpd, but they might be offline for a while before
they get contact to a time server, e.g. because of DSL problems.
Define one of your internal systems as master time server that
connects to other NTP servers outside your
On Friday 04 May 2007 10:07, Christian Schmidt wrote:
Hello Amon,
Amon Ott, 02.05.2007 (d.m.y):
All our systems run ntpd, but they might be offline for a while
before they get contact to a time server, e.g. because of DSL
problems.
Define one of your internal systems as master time
Hello everybody!
Currently, dovecot just kills itself if it detects that time has moved
backwards more than a hardcoded number of seconds. I accept the
reasons, but I do not like to restart dovecot manually after waiting
for time to move forward again. A cron job would not help, because
time
