From owner-freebsd-stable@FreeBSD.ORG Wed Mar 1 12:38:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 058AA16A423; Wed, 1 Mar 2006 12:38:31 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 521AC43D45; Wed, 1 Mar 2006 12:38:20 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id k21Cbfv2080881; Wed, 1 Mar 2006 15:37:41 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id k21CbeoQ080879; Wed, 1 Mar 2006 15:37:40 +0300 (MSK) (envelope-from yar) Date: Wed, 1 Mar 2006 15:37:40 +0300 From: Yar Tikhiy To: Hajimu UMEMOTO Message-ID: <20060301123739.GH63713@comp.chem.msu.su> References: <20060219225701.0e3e244b.rosti.bsd@gmail.com> <20060221165959.GB77513@comp.chem.msu.su> <20060222024430.ad4b5c60.rosti.bsd@gmail.com> <20060223235727.33cddb13.rosti.bsd@gmail.com> <20060224155153.f7da1a52.rosti.bsd@gmail.com> <20060227151954.GV6435@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Cc: freebsd-stable@freebsd.org, freebsd-stable-local@be-well.ilk.org, dwmalone@maths.tcd.ie, Rostislav Krasny , des@des.no, mak@ll.mit.edu, MH@kernel32.de Subject: Re: SSH login takes very long time...sometimes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 12:38:31 -0000 On Wed, Mar 01, 2006 at 12:28:14AM +0900, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Mon, 27 Feb 2006 18:19:54 +0300 > >>>>> Yar Tikhiy said: > > yar> I finally spared some time to test your recent changes and found > yar> that the resolver still would retry using the first, and only the > yar> first, domain on the `search' list when the nameserver was down, > yar> which effectively led to another kind of request doubling. > > yar> A similar effect was observed when a `domain' line was specified > yar> in resolv.conf in place of `search'. > > yar> Is there a real reason to retry with a different domain when the > yar> nameserver doesn't respond at all? > > It seems yet another issue. The errors returned by res_querydomain() > are not handled uniformity. Please try following patch: It works for me, thanks! -- Yar