On May 6, 06:42 UTC, Rini van Zetten wrote: > > when i start ntpd. > > > But when the clock offset is big (1-1-1970 for example), > > > the 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 gets 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 _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
