On Thu, Jun 11, 2009 at 04:08:54PM +0300, David Baron wrote: > >>Has been happening quite a bit lately: > > >>Problem with ntpdate. If and when it finally works, get a change of 10,800 > >seconds ... that is 30 minutes. > > >>The dovecot IMAPd server is unreadable. Restarting it yields a complaint > >>about 10,800 seconds of time, killing itself now! Restarting it again > >>works OK. > > >>What's happening? Bug? Fix? > > >Of course, we are missing the point. No, it is not 30 minutes like my eyes > >fooled me into a cute title. This is three hours and that is a significant > >number. I live at GMT + 2. Add one for daylight savings time. > > >However, I have never used GMT (universal) time to save my system time. > >So why is this happening now? Ntpdate has not been upgraded past few days. > > >... and why should dovecot care? > > OK, time to fix this. Since my system comes up with the "correct" time zone > but three hours later, it must be interpreting the stored (hw) time as GMT > and > adding the three hours (gmt+2 + daylight savings). > > How to fix this? >
Set the computer time to GMT. date -u MMDDhhmmCCYY.ss date -u 061122002009 hwclock --systohc [Sets board hardware clock from the date you just gave.] dpkg-reconfigure -plow tzdata [And give the appropriate time zone offset. I live in UK and keep my time on GMT all year round, so I'd accept GMT here.] HTH, AndyC > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
