On 10/02/15 05:15, [email protected] wrote:
Hi, I'm using the ntpd to sync time. When I change the current date for exampe to
0210020215 (2015-02-10 02:02), the actually current time is 2015-02-10 03:02, then I run
"ntpq -p" for several times, the offset doesn't change at all.
Garbage In Garbage Out.
ntpd is intended in environments where time behaves like time. It
should actually abort in the case you describe, as something has clearly
broken so badly that it is no longer safer to try and discipline the clock.
People often try this as a test, but it is not a valid test.
Basically, up to a lower limit (default 128ms, but significantly
increased by -x) ntpd will slew to correct. Above that limit, up to a
second limit (which I seem to remember to be 10 minutes) it will wait
about 15 minutes to confirm that it really is seeing a step change, then
restart the initial synchronisation and step. Above the second limits,
it should abort, except if you enable an option to allow one such step
and it is the first one.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
