This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: More on SIGINT, longjmp, and getaddrinfo


* Carlos O'Donell:

>> What is the worst cast time for getaddrinfo or getnameinfo to return?  I
>> assume the really nasty case would involve several retransmissions on each of
>> several different steps so the worst case could be horribly long.  How about
>> an estimate for a simple dead-server case?  Is there a limit on the number of
>> steps?  ...
>
> There is a limit.

There is not.  Not with DNS, due to bug 19643.  There is no
overarching timeout for TCP, so you get the kernel default timeout for
the connect call, and potentially no timeout at all if the TCP
connection is silently severed in just the wrong state.

And that's just DNS.  We don't know for certain what other NSS service
modules do.  I have nss_files tests (which I still need contribute)
that take a few dozen seconds to run.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]