Lines Matching +full:system +full:- +full:clock +full:- +full:frequency
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4 <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
12 <!-- #BeginDate format:En2m -->10-Mar-2014 05:07<!-- #EndDate -->
27 … and upgrade circa 2003. Headway violations result in an optional <em>kiss-o'-death</em> (KoD) pac…
31 <h4>5. Frequency File</h4>
32 …frequency training has always been a problem, as it can take a very long time to trim the frequenc…
33 …clock state machine so that, if no frequency file is available, an initial training interval of 30…
34 …frequency error is large, the time offset at the end of the period can be moderately large, which …
35 …frequency file was written at one-hour intervals. This apparently makes embedded systems folks ner…
37 …show leap warning bits or if one or more of the survivors are a reference clock with leap warning …
38 …ons between warnings and no warnings are reported to the protostats file, system log and traps.</p>
39 <h4>7. Orphan Mode and Local Clock Driver</h4>
41 …clock driver can be very dangerous when used as a fallback when connectivity to Internet time serv…
43 …clock filter and resynchronize. Once the client has backed off the poll interval after a lengthy o…
45 <p>In order to speed response to initial startup when a reference clock is available, the clock is …
52 …hanged to fix some very old bugs. The display is now consistent with the system and peer billboard…
53 …itions are reported, including clock state machine changes, mobilization, /demobilization, system …
54 …to this file as reported and optionally to the system log. Many reports that sometimes clog up the…
55 …-6 monitoring protocol was designed circa 1988 the considered intent was that monitoring functions…
56 …rse such things as the flash codes, clock state or anything else not called out in the NTPv4 speci…
57 … scripts should be changed to use only the leap and select fields of the system status word. If th…
58 <h4>11. Two-step and timestamp capture</h4>
59 … was the two-step protocol in which the transmit timestamp is sent in a following message. However…