Please note that this bug is now fixed in glibc 2.9, with the
implementation of unified lookup. Both A and address are looked-up
at the same time (starting with the A query), and the resolver does not
choke anymore on a missing answer.
However the behavior of the resolver will be resto
On Thu, Aug 02, 2007 at 10:19:50PM +1200, Andrew McMillan wrote:
> Package: libc6
> Version: 2.6-5
> Severity: important
> Tags: patch
>
>
> Hi,
>
> Tolleff fog Heen has written a patch for the resolver, so that it does
> not start performing (or waiting for) lookups unless a globally
> sco
Hi,
I've been runing libc6 with Andrew M's patch on a IPv6 enabled AMD64 box
for the past week just fine. IPv6 is still runing just great.
I'll try removing the global IPv6 address soon and see how it runs
without.
Cheers!
--
Andrew Ruthven, Wellington, New Zealand
At work: [EMAIL PROTECTED]
On Thu, 2007-08-02 at 12:30 +0200, Aurelien Jarno wrote:
>
> I have already been given the link to this patch. It sounds reasonable,
> but first I would like to know if it is in use on more than one machine,
> for both IPv4 and IPv4 + IPv6 setups?
>
> I don't really want to apply a patch that can
Andrew McMillan a écrit :
> Package: libc6
> Version: 2.6-5
> Severity: important
> Tags: patch
>
>
> Hi,
>
> Tolleff fog Heen has written a patch for the resolver, so that it does
> not start performing (or waiting for) lookups unless a globally
> scoped IPv6 address is present on some int
Package: libc6
Version: 2.6-5
Severity: important
Tags: patch
Hi,
Tolleff fog Heen has written a patch for the resolver, so that it does
not start performing (or waiting for) lookups unless a globally
scoped IPv6 address is present on some interface.
Since Debian enables IPv6 by default, m
6 matches
Mail list logo
