Hi,
xntpd dies on clinet if gap from server is too large, that's the reason why I asked if the gap is over 15 minutes on my first post.
See also this from man of xntpd:
The NTP daemon has three regimes in which it operates:
offset below 128 milliseconds
This is the normal operating regime of NTP. A properly configured NTP hierarchy (with reasonable networking) can operate for years without ever approaching the 128 millisecond upper limit. All time adjustments are small and smooth (known as SLEWING), and nobody even notices the SLEW adjustments unless they have a cesium clock or a GPS clock and expensive instrumentation to make sophisticated measurements (HP/Agilent makes the instruments).
offset above 128 milliseconds
This regime is often encountered at power-on because, those battery-backed real-time clocks they put in computers are not too great. Because NTP is quite capable of keeping the offset below one millisecond all the time it is running, many users want to get into the normal regime quickly when an offset above 128 millisecond is encountered at startup. So in this situation NTP will (fairly quickly) make a single STEP change, and is usually successful in getting the offset well below 128 millisecond so there will be no more of the disruptive STEP changes.
offset above 1000 seconds
This is so far out of the normal operating range that NTP decides something is terribly wrong and human intervention is required. The daemon shuts down.
1000 seconds are 16 minutes or so, if you have such discrepancy xtnpd will die with a message in syslog.log.
So post:
- reply about the discrepancy between client and server;
- if syslog.log shows something related to xntpd.
HTH.
Best regards,
Fabio
WISH? IMPROVEMENT!
