Hi, We are trying to chose the 'step threshold value' for ntp daemon(ntp client) as 32 msec instead of the default value of 128 msec and do not plan to use -x option. This will help in minimising the number of times we adjust the system clock (as Not using -x option will result in using slew corrections below 32 msec offsets, hence max of 64 consecutive slew corrections and above 32 msec offset will result in step correction) . If anyone knows pluses / negatives of chosing the 'step threshold value' to be 32 msec as mentioned above (given the need to minimise the number of times to adjust system clock) - please let us know. What is the probability of ntp source based UTC time straying beyond 32 msec offsets due to network congestion, jitter - high / medium /low ? NTP documentations available seem to suggest - ntp source based UTC time straying beyond 128 msec is very rare. Any clarifications on this is deeply appreciated. Thanks, Ravi Suhas.P.B Lucent Technologies ST-1, Hosur Road, Bangalore - 560095. Tel: +91-80-51191355 Mobile: +91-9886081128
<http://lucent.com/> Lucent Technologies, Bell Labs Innovations <http://promos.hotbar.com/promos/promodll.dll?RunPromo&El=&SG=&RAND=53408&pa rtner=hbtools> Upgrade Your Email - Click here! _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
