VanLUG Email Archive
inTEXT Communications (list@intextonline.com)
Tue, 20 Oct 1998 09:40:02 -0700 (PDT)
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.
>
> Brian.
>
**********************************************
Mail List Account - Glenn Graham
inTEXT Communications Vancouver BC Canada
Corporate Intranet & Internet Security
System Administration - FireWall Systems
Linux Bsd FreeBSD Programming Perl / c / c++
www.intextonline.com | glenn@intextonline.com
This archive was generated by hypermail 2.0b3 on Mon 02 Nov 1998 - 03:23:17 PST