Date: Fri, 11 Jun 2004 16:20:22 GMT From: "Ralf S. Engelschall" <rse@engelschall.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/67819: libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004 Message-ID: <200406111620.i5BGKMZn017963@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/67819; it has been noted by GNATS.
From: "Ralf S. Engelschall" <rse@engelschall.com>
To: Kris Kennaway <kris@obsecurity.org>
Cc:
Subject: Re: kern/67819: libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004
Date: Fri, 11 Jun 2004 18:16:34 +0200
On Fri, Jun 11, 2004, Kris Kennaway wrote:
> On Fri, Jun 11, 2004 at 08:21:02AM +0200, Ralf S.Engelschall wrote:
>
> > >Fix:
> > I've not investigated what particular MFC between 2-Jun-2004 and
> > 9-Jun-2004 caused this, but backing out this will certainly fix it
> > because using the libc_r.so.4 from 2-Jun-2004 fixes the problem
> > immediately. Sorry, I'm today leaving for holiday so I cannot
> > investigate myself further, but the problematic MFC should be not too
> > hard to find as there were not so much MFCs to libc during the mentioned
> > time range AFAIK.
>
> Wasn't this already fixed? Please cvsup again and confirm.
Yes, as of today (11-Jun-2004 12:00 CET) the RELENG_4 no longer
shows this bug. Sorry, I was not aware that it was already fixed
such fast. Thanks.
Ralf S. Engelschall
rse@engelschall.com
www.engelschall.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406111620.i5BGKMZn017963>