On 12/2/2010 8:16 AM, Richard B. Gilbert wrote: > On 12/1/2010 10:49 PM, Atul Gupta wrote: >> Hi all, >> My ntp client is taking some time before syncing up with the server in >> multicast mode, generally its waiting for 4 packets from server before >> syncing its time, is it normal , and if so , what is the reason for this. > > NTPD is measuring the rate at which your clock ticks. It does not > *just* set the clock, it also attempts to make the clock tick at a rate > of exactly one tick per second! > > You can speed things up a *little* by using the "iburst" keyword in > NTP.CONF. NTPD can take as long as ten hours to achieve the accuracy of > which it is capable. >
I'd be interested in how you imagine it could do that since it is a multicast client and only receives packets rather than sending them! In read-only mode you have to wait until you have received enough packets to fill enough of the pipeline so that an analysis of the data can be done and an estimate of the clock calculated. A multicast server sends at the rate of 1 NTP packet per minute so it takes 4 minutes to get to that point. Danny _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
