[ntp:questions] sanity limit
per at computer.org
Thu Mar 15 07:50:01 UTC 2007
I'm using a Tobit DCF77 receiver, which is a little unstable. This is
quite possibly due to reception - it has frequent periods with no sync.
But, the worst bit is when does sync, and the time received is bogus:
PARSE receiver #1: STATE CHANGE: DST; TIME CODE; (LEAP INDICATION;
ANTENNA) -> TIME CODE; (LEAP INDICATION; ANTENNA)
PARSE receiver #1: SYNCHRONIZED
clock GENERIC(1) event 'clk_okay' (0x00)
peer GENERIC(1) event 'event_peer_clock' (0x85) status 'unreach, conf,
15 events, event_peer_clock' (0x80f5)
peer GENERIC(1) event 'event_reach' (0x84) status 'unreach, conf, 15
events, event_reach' (0x80f4)
synchronized to GENERIC(1), stratum 0
time correction of -1773142096 seconds exceeds sanity limit (1000); set
clock manually to the correct UTC time.
system event 'event_fault' (0x02) status 'leap_none, sync_lf_clock, 15
events, event_peer/strat_chg' (0x2f4)
What can I do to prevent the bogus time correction without having the
NTP daemon stop?
/Per Jessen, Zürich
PS: is this list actively moderated?
More information about the questions