NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/sys/next/sysadmin/4995

Text File | 1992-09-02 | 1.5 KB | 34 lines

Newsgroups: comp.sys.next.sysadmin
Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!usenet
From: [e-mail] (J.B. Nicholson-Owens)
Subject: Easing clock to correct time via ntp
Message-ID: <[e-mail]>
Sender: [e-mail] (Net Noise owner)
Reply-To: [e-mail] (J.B. Nicholson-Owens)
Organization: University of Illinois at Urbana
Date: Wed, 2 Sep 1992 18:11:29 GMT
Lines: 22

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 ([e-mail])
-- no NeXTmail please