Re: [Dovecot] time going back
On Monday of October 29 2007, Timo Sirainen wrote: > More than 5 seconds and Dovecot kills itself. <=5 seconds and Dovecot > logs a warning and sleeps until it's back in present. good to know > > Do you think using -a on rdate would not cause such effect? > It wouldn't, but it would probably take quite a long time. sure > Why don't you just run ntpd to keep the time correct all the time? I do, but firewall misconfiguration blocked it. regards -- Marcin Gryszkalis, PGP 0x9F183FA3 jabber jid:[EMAIL PROTECTED], gg:2532994 http://the.fork.pl
Re: [Dovecot] time going back
On Mon, 2007-10-29 at 03:35 +0100, Marcin Gryszkalis wrote: > btw, while checking results of nightly DST change I re-sync-ed one of my > boxes > to ntp server with rdate and got > > Oct 28 10:32:48 sas dovecot: Time just moved backwards by 1099 seconds. This > might cause a lot of problems, so I'll just kill myself now. > > 1099 seconds is ~18 minutes > > How much is too much for dovecot? More than 5 seconds and Dovecot kills itself. <=5 seconds and Dovecot logs a warning and sleeps until it's back in present. > Do you think using -a on rdate would not cause such effect? > > fyi rdate(8): > -a Use the adjtime(2) call to gradually skew the local time to the > remote time rather than just hopping. It wouldn't, but it would probably take quite a long time. Why don't you just run ntpd to keep the time correct all the time? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] time going back
On Saturday of October 27 2007, Jeff Grossman wrote: > > dovecot killing itself because I manually adjusted the clock in the > > past. Will it not happen in this case? > A timezone time adjustment is not a problem. The time one your computer > is always based on GMT time. The local time is displayed based on your > timezone. It should not have any effect. btw, while checking results of nightly DST change I re-sync-ed one of my boxes to ntp server with rdate and got Oct 28 10:32:48 sas dovecot: Time just moved backwards by 1099 seconds. This might cause a lot of problems, so I'll just kill myself now. 1099 seconds is ~18 minutes How much is too much for dovecot? Do you think using -a on rdate would not cause such effect? fyi rdate(8): -a Use the adjtime(2) call to gradually skew the local time to the remote time rather than just hopping. regards -- Marcin Gryszkalis, PGP 0x9F183FA3 jabber jid:[EMAIL PROTECTED], gg:2532994 http://the.fork.pl
Re: [Dovecot] time going back
zbigniew szalbot wrote: Hi all, Sorry if this is trivial. I am just concerned. In Poland we will be putting the clocks one hour behind (back) on Sunday. I once saw dovecot killing itself because I manually adjusted the clock in the past. Will it not happen in this case? Thanks for your ideas. Zbigniew Szalbot A timezone time adjustment is not a problem. The time one your computer is always based on GMT time. The local time is displayed based on your timezone. It should not have any effect. Jeff
[Dovecot] time going back
Hi all, Sorry if this is trivial. I am just concerned. In Poland we will be putting the clocks one hour behind (back) on Sunday. I once saw dovecot killing itself because I manually adjusted the clock in the past. Will it not happen in this case? Thanks for your ideas. Zbigniew Szalbot
