There's an ntp script available on deadcat that I believe does what you require (warning, html coming up):<br>
<br>
<br>
<a name="begindata"> </a>
<br>
<br>
<center><form action="/hobbit-cgi/bb-hist.sh">                    <input value="HISTORY" type="submit">                         <input name="HISTFILE" value="bb.ntp" type="hidden">                        <input name="ENTRIES" value="50" type="hidden">                     <input name="IP" value="165.221.94.21" type="hidden">
                        <input name="DISPLAYNAME" value="bb" type="hidden">                         </form></center>

<center><table summary="Detail Status" align="center" border="0">
<tbody><tr><td><h3> Tue Jan 24 10:19:52 CST 2006 Clock is synchronized</h3>
<pre><br><br><table width="100%">
<tbody><tr valign="top"><td>Clock offset<br>(ms)</td><td>Jitter<br>(ms)</td><td>Clock drift<br>(ppm)</td><td>Residual drift<br>(ppm)</td><td>Stratum</td></tr>
<tr><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16"> 0.485</td><td>0.126</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16">
 -130.957</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16"> 0.002</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16">
 2</td></tr>
</tbody></table><br><hr><br><br><br><br><br><table width="100%">
<tbody><tr valign="top"><td>Server</td><td>Refid</td><td>Stratum</td><td>Reach</td><td>Delay<br>(ms)</td><td>Jitter<br>(ms)</td><td>Offset<br>(ms)</td><td>Dispersion<br>(ms)</td><td>Status</td></tr>
<tr><td><a href="http://165.221.90.22">165.221.90.22</a></td><td>CDMA</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16"> 1</td><td>377</td><td>0.892</td><td>
0.094</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16"> 0.485</td><td>14.847</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16">
 sel_sys.peer</td></tr>
<tr><td>LOCAL(0)</td><td>LOCAL(0)</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16"> 10</td><td>377</td><td>0.000</td><td>0.008</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/green.gif" alt="green" border="0" height="16" width="16">
 0.000</td><td>0.948</td><td><img src="https://bb.ocio.ad.usda.gov/hobbit/gifs/clear.gif" alt="clear" border="0" height="16" width="16"> unknown</td></tr> </tbody></table><br><br><center>NTP version: ntpd <a href="mailto:4.1.2@1.892">
4.1.2@1.892</a> <br>bb-ntp.sh Version:0.9.2</center><br></pre>
</td></tr></tbody></table>
<br></center>
Thanks,<br>
Larry Barber<br>
<br><br><div><span class="gmail_quote">On 1/24/06, <b class="gmail_sendername">Tracy Di Marco White</b> <<a href="mailto:gendalia@iastate.edu">gendalia@iastate.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>We're a kerberos based shop, which means everything authenticating<br>to kerberos needs to be within 5 minutes of our kerberos server's<br>clock.  We recently had problems with a few important servers having<br>severe time keeping problems, as well as two of our time servers not
<br>keeping sync because of multiprocessor issues.  For a lot of our<br>servers it'd be nice to warn if time is more than a minute or two<br>out from our reference clock on the kerberos servers, and go red at<br>four or five minutes out.  But it'd also be nice to have a warning
<br>if our central time servers are having problems keeping sync, or<br>having other problems (I'm not intimately familiar with ntp, so I'm<br>not sure what problems those could be).<br><br>I think the ntp check right now only checks that ntp is running.
<br>It would be nice to check that there's a valid sys.peer, and maybe<br>some number of acceptable candidates, maybe that the offset and<br>jitter are within some reasonable parameters for the peers/servers.<br><br>I'm mostly just thinking about implementing something like this
<br>at the moment, maybe someone already has this, or maybe there's<br>a better way to think about this, so I'd appreciate input on it.<br><br>Tracy J. Di Marco White<br>Information Technology Services<br>Iowa State University
<br><br>To unsubscribe from the hobbit list, send an e-mail to<br><a href="mailto:hobbit-unsubscribe@hswn.dk">hobbit-unsubscribe@hswn.dk</a><br><br><br></blockquote></div><br>