🚀 go-pugleaf

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.

I don't know if this is true and, therefore, was wondering if it would be  
a good idea to stick an "ntp -s <ntp host>" in as a crontab entry running  
every 10 minutes?   I figure the worst that will happen with this is that  
the clock will be set correctly the first time and never be too far off  
from what time it *really* is.  Unfortunately, if my clock isn't that  
good, it will only be correct on the 10th minute, when it was jerked to  
the correct time.

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?

Thanks.
--
-- Jeff (jeffo@uiuc.edu)
-- no NeXTmail please