[ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread Rob
I while ago I discussed the problem with an ntpd server that has to be synchronized to a GPSDO that provides PPS but no absolute time. After the usual discussion about you should not want that, a solution was finally found using the following tricky workaround: # PPS via ATOM server 127.127.22.0

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread William Unruh
On 2014-07-29, Rob nom...@example.com wrote: I while ago I discussed the problem with an ntpd server that has to be synchronized to a GPSDO that provides PPS but no absolute time. After the usual discussion about you should not want that, a solution was finally found using the following

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread A C
On 2014-07-29 11:33, William Unruh wrote: On 2014-07-29, Rob nom...@example.com wrote: The reasoning is that once the time is locked to PPS, it should remain close enough for the local clock to be trusted as an absolute time source (this system is rarely rebooted). It should do that even

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread Rob
William Unruh un...@invalid.ca wrote: On 2014-07-29, Rob nom...@example.com wrote: I while ago I discussed the problem with an ntpd server that has to be synchronized to a GPSDO that provides PPS but no absolute time. After the usual discussion about you should not want that, a solution was

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread mike cook
Rob, Looks like a bug anterior to your version. I see the same issue with version=ntpd 4.2.6p5@1.2349-o whether or not there is a preferred local clock or not, and whether or not there are other active server associations. One for Harlen if it has not already been flagged. Tue Jul 29

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread William Unruh
On 2014-07-29, A C agcarver+...@acarver.net wrote: On 2014-07-29 11:33, William Unruh wrote: On 2014-07-29, Rob nom...@example.com wrote: The reasoning is that once the time is locked to PPS, it should remain close enough for the local clock to be trusted as an absolute time source (this

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread A C
On 2014-07-29 12:46, William Unruh wrote: On 2014-07-29, A C agcarver+...@acarver.net wrote: On 2014-07-29 11:33, William Unruh wrote: [1] ATOM's own documentation suggest maxpoll of 4 to 6 to keep the clock synced to PPS. But that pins everything else to the same value unless a minpoll is

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread Rob
mike cook michael.c...@sfr.fr wrote: Rob, Looks like a bug anterior to your version. I see the same issue with version=ntpd 4.2.6p5@1.2349-o whether or not there is a preferred local clock or not, and whether or not there are other active server associations. One for Harlen if it has

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread Rob
A C agcarver+...@acarver.net wrote: On 2014-07-29 11:33, William Unruh wrote: On 2014-07-29, Rob nom...@example.com wrote: The reasoning is that once the time is locked to PPS, it should remain close enough for the local clock to be trusted as an absolute time source (this system is rarely

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread Brian Inglis
On 2014-07-29 14:46, Rob wrote: mike cook michael.c...@sfr.fr wrote: Rob, Looks like a bug anterior to your version. I see the same issue with version=ntpd 4.2.6p5@1.2349-o whether or not there is a preferred local clock or not, and whether or not there are other active server

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread Paul
On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis brian.ing...@systematicsw.ab.ca wrote: As I discovered recently under similar circumstances, offline servers are considered falsetickers, and if you have insufficient other candidates, or fewer than 3, nothing gets selected. I don't think I'm

Re: [ntp:questions] LOCL clock reachability not 377?

2014-07-29 Thread Brian Inglis
On 2014-07-29 21:32, Paul wrote: On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis brian.ing...@systematicsw.ab.ca wrote: As I discovered recently under similar circumstances, offline servers are considered falsetickers, and if you have insufficient other candidates, or fewer than 3, nothing gets