Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Excellent, thank you. The link to the bug report is particularly appreciated, though I do wish that the developers explained a bit more clearly why this behavior is intentional -- it seems like the only role of internet servers in a PPS-disciplined system is to disambiguate the seconds and provide sanity checking but otherwise they don't normally contribute to timekeeping (assuming I understand the discipline algorithm correctly). Backing off to longer intervals seems more polite to internet timeservers by reducing unneeded traffic. Commented Feb 21, 2014 at 15:13
  • In regards to the minclock/minsane settings, I don't typically use that many sources: it had added them strictly for testing purposes to see if the polling interval had any dependence on stratum or upstream time source. Additionally, I typically use the 127.127.20.x generic NMEA/PPS driver but switched to the PPS-only driver specifically for testing this issue: by having internet-only (no PPS) and internet-with-PPS configurations I could test the effect of a single change. Adding an extra variable in the form of NMEA would complicate testing. Also, your link #5 doesn't work. Commented Feb 21, 2014 at 15:22
  • A warning about tos minsane 4 minclock 4: If you have only three "sane" time sources, you clock will not sync. It may not be very obvious from the status. However if you are sure you always have that many valid time sources, you can use that. monsanesays how many valid clocks are required, while minclock says how many clocks to consider from the pools. I'd use "minclock >= minsane +2"... Commented Nov 24, 2023 at 8:04