OK, I admit I am new to LINUX, so please help me in setting up my server as NTP client. In the past, I have had the same problem where the time moved backward.
In my case I have only 1 server on which I run everything. Currently this server is setup to synchronize time using the NETWORK TIME PROTOCOL (application which comes with CentOS).
So here is my question: How do I setup this one server as NTP Client? You can point me to a location the NET, where I can read and set it up myself!
Kirt
-----Original Message----- From: dovecot-bounces+kbajwa=tibonline.net@dovecot.org [mailto:dovecot-bounces+kbajwa=tibonline.net@dovecot.org] On Behalf Of Ville Walveranta Sent: Monday, August 18, 2008 2:38 PM To: Dovecot Mailing List Subject: Re: [Dovecot] dovecot: Fatal: Time just moved backwards by 3603seconds.
ntp client as a service (daemon) is the way to go... I had the same problem; I wasn't aware of the fact that dovecot would be sensitive to time going backwards. I was running ntpdate via cron, and the first time the time-check resulted in backwards correction, dovecot bombed. Unless the drift is great and frequent it's not a hardware clock problem as generally the clocks on the PC motherboard drift, and the drift doesn't have to be much when it's to the "wrong" direction (as far as dovecot is concerned). The way ntp handles the correction is very gracefulby speeding up or slowing down the clock (or stepping for greater corrections)that it's recommended even on systems that don't run dovecot. If the drifts are generally nominal, it might be a good idea to use -x (--slew) option to allow adjustment of the common few second corrections more gradually without stepping. Without the "-x" option slew is limited to ±0.128 second corrections and time is stepped even for, say, 3 second corrections. With -x one second correction is completed in about 33 minutes, and greater corrections (up to 600 seconds) take thus days to complete, so the -x option is not good for systems with bad clocks :-).
Ville