🚀 go-pugleaf

In article <BtyqJ7.9vo@news.cso.uiuc.edu> jeffo@uiuc.edu (J.B. Nicholson-Owens) writes:
>I've heard that using a simple "ntp -s" or "ntp -f" isn't good for the  
>system because the clock might jump to the correct time from whatever it  
>was set at before and cause a crontab entry to be skipped.

Yes, this is true.  Its generally pretty rude to just reset the clock
while stuff is running.

>If there is a way to ease the clock forward or backward (accelerate or  
>decelerate the ticking of seconds, I suppose) so that the clock was  
>correct relatively all the time and not pass up any minutes or seconds  
>(thus solving any problem with crontab entries being skipped), how is that  
>done?

You could just run ntpd all the time.  It will constantly correct the
clock while and even estimate the intrinsic drift of the clock
hardware and continue to apply corrections to compenstate even when
the network is unavailable.  

NeXT even thoughtfully provides a hacked version of the NTP software
written by Mike Petry and myself at the University of Maryland.  If
you are serious about time synchronization, you should dump that
version and bring up xntp3 which is the latest and greatest.  It
compiles and runs on a NeXT with no problems, though it doesn't do
anything with netinfo, so you'll have to build an /etc/ntp.conf file
instead.  This is a feature, not a bug.

louie