In article <[EMAIL PROTECTED]> Tom Smith
<[EMAIL PROTECTED]> writes:
>Danny Mayer wrote:
>>
>> I've spent a lot of time debugging this stuff. The fact is that if a
>> server is not reachable in the first place it won't show up in the
>> scoreboard and there is no association created. A refid of 0.0.0.0
>> doesn't mean a lot since we don't know what kind of ntp is responding to
>> the requests. Other implementations may not even set the refid. We don't
>> know since that not a piece of information we've been given.
>>
>
>At least through 4.2.0a, as long as a configured server has an address it
>will show up on the billboard whether it's reachable or not. The only thing
>that keeps it off is a name that doesn't resolve.
I'll raise you one, here is ntp-dev-4.2.0b-20050926:
remote refid st t when poll reach delay offset jitter
==============================================================================
10.1.1.234 .INIT. 16 u - 64 0 0.000 0.000 0.002
10.1.1.235 .INIT. 16 u - 64 0 0.000 0.000 0.002
10.1.1.236 .INIT. 16 u - 64 0 0.000 0.000 0.002
It has surely never received a packet from any of those "servers", since
they simply don't exist.
> I really wouldn't want to
>see it any other way. Otherwise, if your server happens to be down when you
>start, it will never be used.
Absolutely agreed. And even if ntpd kept trying them without showing
them in 'ntpq -p' it would be a loss I think.
--Per Hedeland
[EMAIL PROTECTED]
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
