VanLUG Email Archive
Vincent Janelle (malokai@gildea.net)
Tue, 20 Oct 1998 13:16:35 -0700 (PDT)
I suggest using xntpd for maintaining it. It will maintain the current
clock, even if you aren't online. The other option is to fine tune your
system drift and use netdate. Personally, since xntpd already does this,
it really isn't worth doing the other way for me.
--Vincent Janelle "MCSE = Must Consult Someone Experienced"
--http://random.gimp.org --mailto:random@gimp.org --UIN 20839279
On Tue, 20 Oct 1998, inTEXT Communications wrote:
> Could I perhaps suggest doing this;
>
> I like to use netdate ( A little old fashioned perhaps )
>
> netdate time.u.washington.edu
>
> Run that as a cron every hour
> 00 * * * * /usr/sbin/netdate time.u.washington.edu
>
> And your clocks will be set fine.
>
>
> On 19 Oct 1998, Brian Edmonds wrote:
>
> > Ian Dobson <Ian@fastnet.bc.ca> writes:
> > > so what am I doing wrong if I do a rdate -s ns1.bc.ca then a
> > > /sbin/clock 2 seconds later and they are 2 minutes appart?
> >
> > Your system has two clocks: a hardware clock, and a software clock.
> > Using rdate will set the software clock, while clock reads the hardware
> > clock. The date command reads the software clock. To set your hardware
> > clock from the software clock run "/sbin/clock -w" (add a -u flag if you
> > keep your clocks in UTC).
> >
> > I used to run a regular cron job to rdate off of a remote server then
> > run clock -uw to update the hardware clock. I now run xntpd to keep my
> > clocks up to date since I have a 24x7 network link. BTW, the software
> > clock is set from the hardware clock when the system boots, so it helps
> > to keep them synced.
This archive was generated by hypermail 2.0b3 on Mon 02 Nov 1998 - 03:23:17 PST