Greetings! Looking over your situation...
Brian Foddy wrote: > server 127.127.1.0 # local clock > fudge 127.127.1.0 stratum 10 I'd probably comment these two lines out. I believe they're only useful in cases where you're looking to maintain synchronization in an island that has no better sources. Since you've got Internet connectivity, you can always find a better source. > restrict ntp3.cs.wisc.edu nomodify > restrict ntp.sycharlutheran.org nomodify > restrict clock.nyc.he.net nomodify I'm also not 100% sure, but I believe "nomodify" would cause the NTP daemon to not allow these peers to modify your clock, even if they are specifically listed as servers to poll. > remote refid st t when poll reach delay offset jitter > ============================================================================== > *127.127.1.0 .LOCL. 10 l 32 64 377 0.000 0.000 0.977 > 128.105.37.11 128.105.201.11 2 u 26 256 377 64.117 10503.0 3750.77 > 173.16.32.174 99.150.184.201 2 u 18 256 377 58.125 10599.0 3771.55 > 209.51.161.238 .CDMA. 1 u 16 256 377 68.408 14408.1 6707.28 The far left hand column, the one with the * next to 127.127.1.0, is where you can see what the NTP server thinks about each peer. In this case, 127.127.1.0 is the one ntpd loves (*); the others are being rejected ( ). Not sure why it didn't break until now. :-) -rt -- Ryan Tucker <[email protected]>,<[email protected]> Proprietor, Suspension of Disbelief Technologies Student, MCC Electrical Engineering Technology http://blog.hoopycat.com/ http://twitter.com/hoopycat
signature.asc
Description: OpenPGP digital signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
