In testing with Suse Linux SP1, it appears the remote ntp client does not sync with the ntp server using undisciplined local clock. In my testing I used ntp-4.2.8 and number of other ntps.
The ntpq -p or 'service ntp status' shows:
refid st t when poll reach delay offset jitter
.INIT. 16 u 56 64 0 0.000 0.000 0.000
Any idea why the undisciplined local clock is not working? Some of the documentation state that "Undisciplined Local Clock should generally no longer be used", but I don't find any documentation stating it doesn't work. Appreciate your help on this.
In testing with Suse Linux SP1, it appears the remote ntp client does not sync with the ntp server using undisciplined local clock. In my testing I used ntp-4.2.8 and number of other ntps.
The ntpq -p or 'service ntp status' shows:
refid st t when poll reach delay offset jitter
.INIT. 16 u 56 64 0 0.000 0.000 0.000
Any idea why the undisciplined local clock is not working? Some of the documentation state that "Undisciplined Local Clock should generally no longer be used", but I don't find any documentation stating it doesn't work. Appreciate your help on this.