Opened 12 years ago

Closed 12 years ago

#160 closed enhancement (invalid)

geen nauwkeurige tijd na boot

Reported by: huub Owned by: nobody
Priority: major Milestone: WL-9.0-RELEASE
Keywords: ntpd Cc:
Resource needed to fix:


Op Hybrid Huub Last Changed Rev: 10776
Last Changed Date: 2012-05-10 03:11:15 +0200 (Thu, 10 May 2012)
wordt de tijd bij het booten van een nieuwe softwareconfiguratie niet goed gezet door ntpd. Herstarten van ntpd geeft nauwkeurige tijd (correctie van een seconde of wat).

Change History (1)

comment:1 by rick, 12 years ago

Resolution: invalid
Status: newclosed

ntpdate(8) zet de tijd ruwweg goed. ntpd(8) heeft minimaal een aantal minuten nodig om de tijd aan te passen naar de echte tijd. Met ntpq -np kan je de huidige status van de ntpd(8) zien:

   Tally Codes
     The character in the left margin in the `peers' billboard, called the
     tally code, shows the fate of each association in the clock selection
     process.  Following is a list of these characters, the pigeon used in the
     rv command, and a short explanation of the condition revealed.

     space   (reject) The peer is discarded as unreachable, synchronized to
             this server (synch loop) or outrageous synchronization distance.

     x       (falsetick) The peer is discarded by the intersection algorithm
             as a falseticker.

     .       (excess) The peer is discarded as not among the first ten peers
             sorted by synchronization distance and so is probably a poor can-
             didate for further consideration.

     -       (outlyer) The peer is discarded by the clustering algorithm as an

     +       (candidat) The peer is a survivor and a candidate for the combin-
             ing algorithm.

     #       (selected) The peer is a survivor, but not among the first six
             peers sorted by synchronization distance.  If the association is
             ephemeral, it may be demobilized to conserve resources.

     *       (sys.peer) The peer has been declared the system peer and lends
             its variables to the system variables.

     o       (pps.peer) The peer has been declared the system peer and lends
             its variables to the system variables.  However, the actual sys-
             tem synchronization is derived from a pulse-per-second (PPS) sig-
             nal, either indirectly via the PPS reference clock driver or
             directly via kernel interface.

Source: man ntpq(8)

Note: See TracTickets for help on using tickets.