Quoting Rob (nom...@example.com):
> >| root@dns1:~# ntpq -c lpeers
> >| ===
> >| *someserver.tld .PPS.
> >| +someserver2.tld .GPS.
> >| -someserver3.tld .PPS.
> >| dns2.dns.dmz.bi 172.2.53.81
> >| dns3.dns.dmz.bi 172.2.53.81
> >| +someserver4.tld .PPS.
> So in the abo
Sander Smeenk wrote:
> Hi,
>
> I'm running four NTP-servers. One has a PPS and is stratum-1, the other
> three sync from that one primarily and have a few out-of-band fallback
> servers configured. This seems to work fine.
>
> However, if i check 'ntpq -c lpeers' on one of the three stratum-2
> se
On 31/03/14 16:32, Sander Smeenk wrote:
However, if i check 'ntpq -c lpeers' on one of the three stratum-2
servers i see an IP-address listed as 'refid' for the 'peer'-entries
in my configuration. This IP-address is not used in any of my
configurations, no traffic is flowing to- or from that IP
Hi,
I'm running four NTP-servers. One has a PPS and is stratum-1, the other
three sync from that one primarily and have a few out-of-band fallback
servers configured. This seems to work fine.
However, if i check 'ntpq -c lpeers' on one of the three stratum-2
servers i see an IP-address listed as
In article , William Unruh
wrote:
> On 2014-03-30, Joe Gwinn wrote:
> > Magnus,
> >
> > In article <53375aba.5070...@rubidium.dyndns.org>, Magnus Danielson
> > wrote:
> >
> >> On 24/03/14 14:38, Joe Gwinn wrote:
[snip]
> >> [MD] The *one* thing you can figure out with more measurements is how
