cdcc info and rtt don't query all servers in the map

On Oct 29, 2004, at 16:28, Vernon Schryver wrote:

>> #      25% of  8 requests ok   10.49 ms RTT              8 ms queue 
>> wait
>
>> Note that cdcc claims that dcc1.dcc.xs4all.nl was 'not answering' at
>> this time. It most definitely was. A tcpdump of traffic to or from
>> 194.109.22.195 from the host that this command was run on, shows no
>> packets being sent to that server at all. A random check indicates 
>> that
>> more of our dcc client installations exhibit this behaviour, although
>> apparently not all.
>>
>> Is that intended behaviour? Does this not cause that last server to
>> never be picked by the client as the server to send it's reports to?
>
> How do you figre that the fifth system was in fact answering?

Because it looks fine from other hosts, which have dcc1 through dcc5 in 
a different order in the map.
It's not specific to this host; it's specific to the 5th entry in many 
maps in our client cluster.

> Did `cdcc "host dcc1.dcc.xs4all.nl; rtt"` get answers?

I had not tried that. That does get an answer:

# cdcc 'host dcc1.dcc.xs4all.nl; rtt'

dcc1.dcc.xs4all.nl,-        anon
# * 194.109.22.195,-                                           XS4ALL 
ID 1118
#     100% of  1 requests ok   50.38 ms RTT             50 ms queue wait

> Are you running FreeBSD 4.10?

Sorry, I should have specified:

$ dccproc -V
1.2.48
  $ uname -rmps
FreeBSD 4.10-RELEASE i386 i386

> This week I finally got around to doing
> somet tests with FreeBSD 4.10 and found that UDP socket disconnecting
> is indeed newly broken in FreeBSD 4.*.  One symptom is that `cdcc rtt`
> overlooks all servers after the first one that does not answer.
> I will release 1.2.58 with a work-around later today.

Excellent; I will try that, then.

Thanks,
-- 
Vincent Schonau