* Gary Turner (kk5st@swbell.net) [020801 23:42]: > On Fri, 02 Aug 2002 08:10:34 +0200, martin f krafft wrote: > > >also sprach R. Bradley Tilley <rtilley@vt.edu> [2002.08.01.1422 +0200]: > >> Is your local time more than 20 minutes off? If so, I think the sync will fail > >> and ntpd will die. I had this problem once before, but once I got my local > >> time within 5 mins of the ntp server time, everything worked just fine. > > > >nope. maybe 20 seconds... but not more. > > When I first started ntpd, it seemingly did nothing to correct the badly > off clock on my machine. I didn't have time or desire to mess with it > then, so forgot it. About 2 days later, I noticed that the time had > been corrected. > > My admitted abysmal ignorance should be allowed for, but my > understanding is that only a small slewing of the clock rate can be done > at each connection. That's so for ntpd (and not really at each connection, it keeps working over time, sending back and forth udp packets to keep in sync as long as the daemons are running). ntpdate is intended to set the local clock from the remote ntp server so that ntp can then be used thereafter to keep them in sync. I think so far every reply in this thread has spoken to ntpd and not ntpdate. Unfortunately for martin, that right there is about the extent of my knowledge on the subject, and I don't know why ntpdate wouldn't synchronize. good times, Vineet -- http://www.doorstop.net/ -- "As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously." --Benjamin Franklin
Attachment:
pgpTtMq4MWVbO.pgp
Description: PGP signature