From owner-freebsd-bugs@freebsd.org  Tue Mar  8 12:08:03 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6588AC7F2B
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  8 Mar 2016 12:08:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B6CB2AD9
 for <freebsd-bugs@FreeBSD.org>; Tue,  8 Mar 2016 12:08:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u28C83mp099457
 for <freebsd-bugs@FreeBSD.org>; Tue, 8 Mar 2016 12:08:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 207804] nscd negtive cache do not timeout for getaddrinfo:Non
 -recoverable failure in name resolution
Date: Tue, 08 Mar 2016 12:08:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: amutu@amutu.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207804-8-aO0nW0amFl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207804-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-207804-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2016 12:08:03 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207804

--- Comment #1 from Jov <amutu@amutu.com> ---
(In reply to Jov from comment #0)

you can ping www.google.com after you recover the /etc/resolv.conf content,=
but
psql can not resolve the error.I read the psql code,and find it use getaddr=
info
to resolve the addr.

this bug happened for my home router several times and one vps a a time.=20

I have coredump for nscd,and I can gdb for the psql or nscd process for more
info if some one need.

--=20
You are receiving this mail because:
You are the assignee for the bug.=