[lug] NTP Configuration

Nate Duehr nate at natetech.com
Thu Sep 27 15:35:39 MDT 2001


And on Debian (cause I think that's what you're using) if your clock is
off by more than five minutes (if I remember correctly) xntpd will do
the "right thing" and NOT synch your clock, assuming something is REALLY
wrong.  

Do an ntpdate time-a.nist.gov or whatever time server you like to get
the clock in sync then /etc/init.d/ntp restart and watch the log files
in /etc/ntp (on Debian if you haven't changed the default configs) to
see if you get an in synch message -- it can take a little while even if
you just did the ntpdate.

On Wed, Sep 26, 2001 at 10:18:25AM -0600, Kevin Fenzi wrote:
> >>>>> "Glenn" == Glenn Murray <gmurray at Mines.EDU> writes:
> 
> Glenn> No luck, the /etc/ntp.conf server time-c.timefreq.bldrdoc.gov
> Glenn> #server time-b.timefreq.bldrdoc.gov #server
> Glenn> time-a.timefreq.bldrdoc.gov server time.nist.gov server
> Glenn> utcnist.colorado.edu driftfile /var/lib/ntp/ntp.drift
> Glenn> #dirfitfile /etc/ntp/drift authenticate no
> 
> Glenn> still gives
> 
> Glenn> $ sudo ntpdate -v 26 Sep 09:14:07 ntpdate[556]: no servers can
> Glenn> be used, exiting
> 
> note that ntpdate is a command line tool, and doesn't read the config
> file. If you run ntpdate you should do:
> 
> ntpdate time.nist.gov
> 
> (or whatever server you want to sync to). 
> 
> To see your config file working you need to start the xntpd and wait a
> bit and should see syslog messages from it about being synced. ;) 
> 
> kevin
> -- 
> Kevin Fenzi
> MTS, tummy.com, ltd.
> http://www.tummy.com/  KRUD - Kevin's Red Hat Uber Distribution
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.



More information about the LUG mailing list