On Fri, 20 Sep 2002, Len Conrad wrote: Sorry about this late response. I'd finished the letter, about to send and my dialup quota kicked my off. In Australia, dialup is still quite popular due to ridiculous prices for even capped broadband.
> > >I think the problem could be the -d (debug) option to ntpdate. Try > > # rm /etc/localtime > # ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime > # ntpdate time.nist.gov > 20 Sep 08:42:52 ntpdate[71492]: step time server 192.43.244.18 offset > 1784.223346 sec > > but the correct time is 09:12 This is expected. 8:42 is the time (as your system reports) that you run ntpdate with consideration to your timezone. The offset is the difference between your system's clock and GMT. It is reporting about 30 minutes of difference when you run the command but, if things are working as they should, your new system clock should be adjusted by this amount. Consequently, if you execute the command again ntpdate time.nist.gov the offset should be something pretty close to zero and things should be fine. If not, and you are running the commands as root, then I have no idea what is wrong. Very puzzling. The only other suggestion I would make is that you run ntpd as a substitute for ntpdate. killall nptd; ntpd -q after making an /etc/ntp.conf file. Something like this should do the trick although you may want to add more servers. server time.nist.gov driftfile /var/db/ntp.drift logfile /var/log/ntp.log authenticate no Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
