[NTLUG:Discuss] Clock issue

[Richard Geoffrion]

Schedule this command in cron

<command>
/usr/sbin/ntpdate time.nist.gov 1> /dev/null 2> /dev/null
</command>

to sync your time with the clock in bolder. Of course you'll have to verify
the presense and location of your ntpdate command.

Visit http://www.boulder.nist.gov/timefreq/service/its.htm to read up about
NTP and find alternate time sources.


----- Original Message -----
From: "Chris Cox" <cjcox at acm.org>
To: <discuss at ntlug.org>
Sent: Friday, June 01, 2001 4:42 PM
Subject: Re: [NTLUG:Discuss] Clock issue


> I noticed under certain loads, the clock doesn't keep up.
> Before everyone cries.... Solaris will do the same thing.
> What I did was use NTP (xntp...whatever) to sync to a
> reliable time source.  Alternatively, you can grab and
> sync from the hw clock... but that's probably not as nice
> in a production environment.... but good enough for
> home use.
>
> "George E. Lass" wrote:
> >
> > Can't help you with why, but you could fix the difference by running
> > hwclock --utc --hctosys
> > periodically as a cron job.
> > If your hwclock is not using utc then omit --utc from the above command.
> >
> > If you are connected to the 'net full time you might also want to check
> > out
> > xntp.
> >
> > George
> >
> > WILLIAM PEARSON wrote:
> > >
> > > Hello,
> > >
> > > I'm running Red Hat 6.0 and my system clock is running about 15-20
minutes
> > > slow. When I go into the system CMOS the time is correct. What could
be
> > > causing this and how can I fix it? It has been this way since I
installed
> > > the OS.
> > >
> > > William Pearson
> > >
> > > _______________________________________________
> > > http://www.ntlug.org/mailman/listinfo/discuss
> > _______________________________________________
> > http://www.ntlug.org/mailman/listinfo/discuss
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>