From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 23:18:19 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A7AD16A403 for ; Sun, 22 Oct 2006 23:18:19 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 8492D43D97 for ; Sun, 22 Oct 2006 23:18:11 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 19106 invoked by uid 399); 22 Oct 2006 23:18:10 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 22 Oct 2006 23:18:10 -0000 Message-ID: <453BFC2A.5010501@FreeBSD.org> Date: Sun, 22 Oct 2006 16:18:02 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Andy Fawcett References: <20061022095811.GA10743@zaphod.nitro.dk> <1161515330.751.9.camel@localhost> <200610221423.19817.andy@athame.co.uk> In-Reply-To: <200610221423.19817.andy@athame.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Hajimu UMEMOTO , "Simon L. Nielsen" , Joel Dahl Subject: Re: Resolver not always resolving hostnames X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2006 23:18:19 -0000 Andy Fawcett wrote: > I'm only seeing this effect (or maybe only noticing it) with csup/cvsup. > Could be coincidence though. Hrrm, it's odd that it affects both csup _and_ cvsup, since the former is written in C, and links natively against our libraries. I'm wondering if we're seeing a situation where the name servers that those hostnames are delegated to are just taking a long time to respond, and neither app is patient enough. I think it would be an interesting experiment to see what happens if you increase the retry timeout. Is anyone else seeing this problem with other applications? Simon, I'll address your problems with host(1) in a separate mail. Doug -- This .signature sanitized for your protection