Subject: Re: ntpq regression (?)
To: None <current-users@netbsd.org>
From: Jukka Salmi <j+nbsd@2006.salmi.ch>
List: current-users
Date: 06/18/2006 15:36:31
Jukka Salmi --> current-users (2006-06-15 20:56:32 +0200):
> Hi,
> 
> since upgrading ntpd (from 4.2.0-r to 4.2.2-o) `ntpq -pn' reports:
> 
> $ ntpq -pn
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> #212.254.26.76   213.144.132.251  3 u   26   64  377    0.204   87.820  10.383
>  212.254.26.75   212.254.26.76    4 u   11   64  377    0.226   83.891   7.109
> 
> The `selected' peer ('#') used to be a `sys.peer' ('*'), and the
> `reject' peer (' ') used to be a `candidat' ('+').

After restarting ntpd I see

$ ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*212.254.26.76   195.216.80.207   3 u    1   64   37    0.206    0.129   7.519
+212.254.26.75   212.254.26.76    4 u    1   64   37    0.184   -2.813   5.601

However, after the next ntpd restart `ntpq -pn' output was again as
reported in the first post...


Regards, Jukka

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~