Thank you for the information. There's a lot of information there but I could not find what exactly what the "state" variable means from the output of ntpq -c rv.
The only candidate information I could find might be peer status from RFC-1305 B.2.2. However, if that does correspond to the state, then it still doesn't give me the information I need. Especially what the difference between 2, 3, 4 mean. 4 is just listed as "reserved" and nothing else there. But ntpd does differentiate between 3 and 4 and I need to know if that's significant in our application. Thanks, Joel Shellman --- "David L. Mills" <[EMAIL PROTECTED]> wrote: > Joel, > > 1. The procedures and algorithms briefing and > related briefings on the > NTP project page. > 2. The ntpq documentation. > 3. The rfc-1305 Appendix B. > > Dave > > Joel Shellman wrote: > > What are the meanings of the states 1, 2, 3, 4 in > the > > output of ntpq -c rv? > > > > I'm working on a little monitor script with strict > > guidelines of ensuring the client is in sync with > the > > server. > > > > So far, I think that if state != 4 or reach & 1 != > 1 > > then I can flag an error, but I notice it drops > into > > state 2 sometimes and wanted to understand that > > better. > > > > Also, I'm trying to figure out how best to deal > with > > the ramp up until it gets to 4 (which it might not > > ever and so I need to flag an error at some > point--but > > when?) __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
