RE: [MLUG - DISCUSSION] time.missouri.edu

["Anderson, Bill" <EMAIL:PROTECTED>]

Why not use NTP? It is more accurate, within a few milliseconds usually. You
can synchronize with more than one time server simultaneously, making your
time even more stable. Plus, you don't have to worry about creating a cron
job. At the longest interval, the time is updated every 1024 seconds (17
minutes).

Bill Anderson

-----Original Message-----
From: EMAIL:PROTECTED
[mailto:EMAIL:PROTECTED]On Behalf Of Michael
Sent: Thursday, November 01, 2001 10:15 AM
To: EMAIL:PROTECTED
Subject: Re: [MLUG - DISCUSSION] time.missouri.edu


I adjust mine every hour. I run a lot of programs that depend on time in
seconds or microseconds to do certain things so I feel it's worth the
small effort of having an rdate cron job. Given the low overhead of
syncing your clock why not update frequently?

*^*^*^*
Michael McGlothlin <EMAIL:PROTECTED>
http://mlug.missouri.edu/~mogmios/projects/

On Thu, 1 Nov 2001, Mikhail Kovalenko wrote:

> Mike Miller wrote:
> 
> > I've been trying to update my time (using a root crontab) every two
hours
> > at 10 mins past the hour from time.missouri.edu, but, strangely, it has
> > been working for me only at 10:10 am for the past two days -- all other
> > times show an error that looks like this:
> 
> Mike,
> 
> What do you do with your computer that you lose so much time every two
> hours that you have to adjust it? Wouldn't once a day be enough?
> 
> -- 
> MK
> --
> To unsubscribe, go to http://mlug.missouri.edu/members/edit.php
> 
> Archives are available at http://mlug.missouri.edu/list-archives/
> 

--
To unsubscribe, go to http://mlug.missouri.edu/members/edit.php

Archives are available at http://mlug.missouri.edu/list-archives/
--
To unsubscribe, go to http://mlug.missouri.edu/members/edit.php

Archives are available at http://mlug.missouri.edu/list-archives/