David Woolley wrote: > BlackList wrote: >> >> Add to both?: >> tos cohort 1 orphan 11 >> restrict source nomodify >> > If he's offline to the ubuntu server, won't that, effectively, > make both server lines redundant, > or does orphan require a token server.
If (#ip: 192.168.17.11) can't reach ntp.ubuntu.com ever, having "server ntp.ubuntu.com" in the conf is obviously useless. > One problem I see is that there is no guarantee which machine will > be the master in the relationship. <http://www.eecis.udel.edu/~mills/ntp/html/orphan.html> {He didn't mention using any automatic server discovery pool / manycast / multicast / broadcast / anycast / ... in his conf.} If he is not using any Automatic Server Discovery, the (#ip: 192.168.17.22) client conf, would need the "server 192.168.17.11" line ? (#ip: 192.168.17.11) doesn't know about (#ip: 192.168.17.22), if it ever gets to talk to "server ntp.ubuntu.com", so much the better; if not, it should chug along on its own. (#ip: 192.168.17.22) has "server 192.168.17.11" in the conf it should follow (#ip: 192.168.17.11) {"the master"} >> and start ntpd with?: -g So, if when ntp is started, if the offset between the client (#ip: 192.168.17.22) and server (#ip: 192.168.17.11) exceeds the panic threshold, ntp will step the client #ip: 192.168.17.22) to match the server (#ip: 192.168.17.11), instead of exiting. -- E-Mail Sent to this address <[email protected]> will be added to the BlackLists. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
