On 2010-05-22, Mr. James W. Laferriere <[email protected]> wrote: > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without MIME-aware tools. > > --566704117-1969238047-1274552283=:21754 > Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed > Content-Transfer-Encoding: quoted-printable > X-MIME-Autoconverted: from 8bit to quoted-printable by ns3.baby-dragons.com id > o4MIHxe1030135 > > Hello Dave , > > On Sat, 22 May 2010, Dave Hart wrote: >> On May 6, 06:42=A0UTC, Rini van Zetten wrote: >>>> =A0when i start ntpd. >>>>> But when the clock offset is big (1-1-1970 for example), >>>>> =A0the ntpd refuses to use the gps reference clock. >>>>> Using the "-g" option does not make any difference. >>>> Does -g -q -x before starting NTPd as a service not get you there? >>> >>> This does also not work. Thanks all for you input. >>> >>> I'm afraid i have to add a workaround in my application which also get= > s the gps input, >>> to set the time when it's more then 4 hours away from gps time. >> >> I think a better answer is to disable ntpd's "panic" threshold >> entirely with "tinker panic 0" in ntp.conf. >> >> Hoping to stick a fork in the meat of this conversation, >> Dave Hart > Can you please share any good AND bad side effects from adding this=20 > option to our conf files ? > I do not have enough knowledge about the internals of ntpd to make head= > s=20 > or tail what side effects there may be form this .
The side effect is that if the time diverges by more than 4 hr, ntp will keep running ( and should step the clock at its first opportunity because 4hr>128ms) > _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
