<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 7/22/2024 10:08 AM, Dave Hall via users wrote:
<blockquote type="cite"
cite="mid:CAPg_kBaKn43i5=K2EhZOb6qJhdnHNJGuARBGhdXnKC1yytRfpw@mail.gmail.com">
<div dir="ltr">
<div>On my secondaries, I have:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><font face="monospace">driftfile
/var/lib/ntpsec/ntp.drift</font></div>
<div><font face="monospace">leapfile
/usr/share/zoneinfo/leap-seconds.list</font></div>
<div><font face="monospace">statistics loopstats peerstats
clockstats</font></div>
<div><font face="monospace">filegen loopstats file loopstats
type day enable</font></div>
<div><font face="monospace">filegen peerstats file peerstats
type day enable</font></div>
<div><font face="monospace">filegen clockstats file clockstats
type day enable</font></div>
<div><font face="monospace">tos maxclock 11</font></div>
<div><font face="monospace">tos minclock 4 minsane 3</font></div>
<div><font face="monospace">pool <a
href="http://ntp-core.cs.binghamton.edu"
moz-do-not-send="true">ntp-core.cs.binghamton.edu</a>
iburst</font></div>
</blockquote>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><font face="monospace">server primary1.x.x.x iburst</font></div>
</blockquote>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><font face="monospace">server primary2.x.x.x iburst</font></div>
</blockquote>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><font face="monospace">restrict default kod nomodify
nopeer noquery limited</font></div>
<div><font face="monospace">restrict 127.0.0.1</font></div>
<div><font face="monospace">restrict ::1</font></div>
</blockquote>
</div>
</blockquote>
<br>
<font face="monospace">You might consider re-ordering your file to
have your own primaries first; my understanding, potentially
flawed, <br>
is that ntp.conf is read 'in order' on startup, so having the
'pool' entry first means it will be checked before the others on
startup. Pool entries randomly incur a lot of DNS lookup overhead
on startup (in my experience). Another of my potentially flawed
understandings is that while three sources is required, four
sources is optimal. You might throw in a reasonably reliable
individual stratum two server to your mix. While it's terribly
larded-up with ancient and dead server listings,
<a class="moz-txt-link-freetext" href="https://support.ntp.org/Servers/StratumTwoTimeServers">https://support.ntp.org/Servers/StratumTwoTimeServers</a> is an
otherwise good resource for that.<br>
<br>
Also set minpoll/maxpoll for the primary lines to query those more
frequently.<br>
<br>
On one of my lan devices that queries my own GPS disciplined
timeserver (also on the lan), I use this:<br>
<br>
server 192.168.1.10 minpoll 3 maxpoll 10 iburst <br>
server clock.sjc.he.net minpoll 6 maxpoll 10 iburst # San
Jose 216.218.254.202 <br>
server timekeeper.delphij.net minpoll 6 maxpoll 10 iburst #
Fremont 64.62.153.210 <br>
server dmz2.la-archdiocese.net minpoll 6 maxpoll 10 iburst # Los
Angeles 205.161.200.3<br>
<br>
Obviously you'd use more geographically adjacent sources.<br>
<br>
Whether any of this advice would resolve the problem, I dunno.
Good luck.<br>
</font>
<pre class="moz-signature" cols="74">--
Paul Theodoropoulos
<a class="moz-txt-link-abbreviated" href="http://www.anastrophe.com">www.anastrophe.com</a></pre>
</body>
</html>