In the case of Solaris 9, If we turn slewalways option on, xntpd will try to always slew the time and will never make large steps backwards or forwards. And also we have to set "disable pll". Because without this option xntpd will not be able to correct time differences greater than 128ms.
Now, When we turn slewalways option on, we do not have to set "disable pll". Because xntpd can correct time differences greater than 128ms even without this option. But, for a reap second insert event, I think we have to set "disable pll" option. Without this option xntpd will make steps backwards even though slewalways is on. No check of slewalways status at http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/xntpd/xntpd/ntp_loopfilter.c#329. And, although slewalways option is on (with disable pll), step_systime() function will not execute in the leap_process(). So, synchronization will not happen just after leap second insert. I have to wait about 15min before start synchronization. Why xntpd is implemented like that? -- This message posted from opensolaris.org
