Comment 24 for bug 229632

Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :

Try with and with out ntpd "-N" option.

Use "ntpq -p" or "ntpdc -c peers" to view the polling interval. Both reports have a "poll" column which is the sleep time in seconds between requests being sent out over the network to the upstream NTP source.

The "poll" column will eventually change from 64 to 128 then 256 through 1024. This change can take hours or even days to occur as the clock stabilizes.

Without "-N" I haven't seen the polling interval get to 1024 on my systems as process preemption destabilizes ntpd too much.