Re: Again ... Re: security.debian.org
> Matus UHLAR - fantomas wrote:
> > However this does not _seem_ to be enough, and I guess it's due to "feature"
> > of glibc, that sorts IP addresses from numerically lowest one to numerically
> > highest one (so it spoils attempts for DNS load-balancing), so if any program
> > is the order of addresses returned via gethostbyname() or getnameinfo(), it
> > tries them always in the following order:
> > % getent hosts security.debian.org
> > 126.96.36.199 security.debian.org
> > 188.8.131.52 security.debian.org
> > 184.108.40.206 security.debian.org
> > so no wonder _if_ 220.127.116.11 is loaded more than other servers.
> > many times I have to re-try update/upgrade to ask other servers and
> > 18.104.22.168 seems to be the slowest for me.
On 29.03.07 13:42, virendra rode // wrote:
> I was under the impression that why netselect (picks closets and fastest
> server) was implemented.
I'm sure it was not implemented to avoid lame feature of glibc. You can't
run netselect before any of e.g. DNS lookup or TCP connect to a server who
has more than one address.
Matus UHLAR - fantomas, email@example.com ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
He who laughs last thinks slowest.