Hi,

for a long time I did not try newer versions of ntpd. However recently I tried
the version from SuSE Linux 9.2 with autokey (requires update from SuSE) from
a startum-1 GPS source. I notices that even when the "peer poll" was 64s, the
loopstats file wasn't updated in that period. Furthermose the update interval
for loopstats is more around 640 seconds rather than 64 seconds.

Can someone explain?

Also syncing with autokey seems to take much longer than without. I have no
understanding of autokey yet, but this seems a bit odd to me.

Regards,
Ulrich

Ulrich,

Not all messages received from servers result in an update to the system 
clock. This has always been the case and is very definitely intentional. 
   Only those messages that do result in update result in loopstats 
messages. See the briefings at the NTP project page. The Autokey 
provision has nothing to do with this issue, other than the fact the 
security protocol does require three to five message exchanges 
piggybacked on the time exchanges.

Dave

Ulrich Windl wrote:
> Hi,
> 
> for a long time I did not try newer versions of ntpd. However recently I tried
> the version from SuSE Linux 9.2 with autokey (requires update from SuSE) from
> a startum-1 GPS source. I notices that even when the "peer poll" was 64s, the
> loopstats file wasn't updated in that period. Furthermose the update interval
> for loopstats is more around 640 seconds rather than 64 seconds.
> 
> Can someone explain?
> 
> Also syncing with autokey seems to take much longer than without. I have no
> understanding of autokey yet, but this seems a bit odd to me.
> 
> Regards,
> Ulrich