Suppose you have server A and server B. Server B is running 60
seconds too fast, while server A is accurate. Is there a way to
gradually move server B's time back into sync with server A, without
making a drastic, immediate change to the clock? In other words, we
would like to 'smear' the
On Tue, Sep 4, 2012 at 12:17 PM, Sean Carolan scaro...@gmail.com wrote:
Suppose you have server A and server B. Server B is running 60
seconds too fast, while server A is accurate. Is there a way to
gradually move server B's time back into sync with server A, without
making a drastic,
This is already how ntpd works. When you first start the service
(usually upon reboot), it will use 'ntpdate' to do a hard set of the
clock, then ntpd picks up and adjusts the clock back and forth to keep
it correct.
My understanding was that ntpd will use slewing for adjustments of
less
What I'm trying to avoid is abruptly resetting the clock from 12:06 to
12:05 all at once. Instead we want to slowly turn the clock back that
one minute, but spread the changes across several hours or days.
I think the -x option may be our solution; I R'd the FM and it says:
...If the -x
4 matches
Mail list logo
