23 Sep
2011
23 Sep
'11
3:51 p.m.
Hello,
On Tue, Sep 20, 2011 at 10:45:23PM +0100, Mathew Newton wrote:
That's fine with me. Whilst it's a pain,
it's really not life or death in
my case.
In the mean time you could try starting ntpd with the -x argument
(keeping the usual -g as well):
-x Normally, the time is slewed if the offset is less than
the step threshold, which is 128 ms by default, and
stepped if above the threshold. This option sets the
threshold to 600 s, which is well within the accuracy
window to set the clock manually. Note: Since the slew
rate of typical Unix kernels is limited to 0.5 ms/s, each
second of adjustment requires an amortization interval of
2000 s. Thus, an adjustment as much as 600 s will take
almost 14 days to complete. This option can be used with
the -g and -q options. Note: The kernel time discipline
is disabled with this option.
AFAIK that would cause your ntpd to slow time down in order to
correct a ~47 second gain, instead of stepping it backwards all at
once. The downside would of course be that your clock would be fast
by a decreasing fraction of 47 seconds for the next ~26 hours.
On Debian and Ubuntu you can find the default ntpd arguments in
/etc/default/ntpd.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting