[email protected] said: > Does the new pool command throw out servers that don't reply?
Yes. I'm not sure of the details, but if you turn on lots of logging and poke around in your log file you will see things like this: [murray@jim ~]$ grep 50.116.55.161 /var/log/ntpd.log 12 Mar 01:02:29 ntpd[470]: Soliciting pool server 50.116.55.161 12 Mar 01:02:29 ntpd[470]: 50.116.55.161 0011 81 mobilize assoc 65182 12 Mar 01:02:30 ntpd[470]: 50.116.55.161 0024 84 reachable 12 Mar 01:05:47 ntpd[470]: 50.116.55.161 0014 84 reachable 12 Mar 02:01:18 ntpd[470]: 50.116.55.161 0014 84 reachable 12 Mar 05:35:59 ntpd[470]: 50.116.55.161 142a 8a sys_peer 12 Mar 06:54:53 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 09:07:25 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 09:40:43 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 10:16:14 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 11:11:03 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 11:53:14 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 17:37:14 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 18:13:13 ntpd[470]: 50.116.55.161 141a 8a sys_peer 12 Mar 23:31:14 ntpd[470]: 50.116.55.161 1525 85 restart timeout 12 Mar 23:31:14 ntpd[470]: 50.116.55.161 0032 82 demobilize assoc 65182 12 Mar 23:31:14 ntpd[470]: 50.116.55.161 local addr 192.168.1.109 -> <null> [murray@jim ~]$ [murray@jim ~]$ grep :: /var/log/ntpd.log 11 Mar 19:37:13 ntpd[470]: Listen normally on 5 wlan0 [fe80::21c:bfff:fe14:be20%3]:123 11 Mar 19:38:13 ntpd[470]: Soliciting pool server 2001:470:1:24f::2:3 11 Mar 19:39:20 ntpd[470]: Soliciting pool server 2607:f740:e::f7d 12 Mar 01:01:37 ntpd[470]: Soliciting pool server 2600:3c03::f03c:91ff:fedf:9b 84 [murray@jim ~]$ That system has IPv6 on the local LAN, but no outside connectivity. -- These are my opinions. I hate spam. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
