From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 20:49:06 2011 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDAE71065673 for ; Thu, 17 Feb 2011 20:49:06 +0000 (UTC) (envelope-from dougb@dougbarton.us) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 4B2658FC14 for ; Thu, 17 Feb 2011 20:49:06 +0000 (UTC) Received: (qmail 29316 invoked by uid 399); 17 Feb 2011 20:20:59 -0000 Received: from router.ka9q.net (HELO ?192.168.2.9?) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 17 Feb 2011 20:20:59 -0000 X-Originating-IP: 75.60.237.91 X-Sender: dougb@dougbarton.us Message-ID: <4D5D832A.8060903@dougbarton.us> Date: Thu, 17 Feb 2011 12:20:58 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Steven Hartland References: <20100909131017.GO4404@twoquid.cs.ru.nl> <20100909140529.GB76889@icarus.home.lan> <201102171158.24636.jhb@freebsd.org> <4215B319C85B46A0AC539A67BC9EAF3C@multiplay.co.uk> In-Reply-To: <4215B319C85B46A0AC539A67BC9EAF3C@multiplay.co.uk> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Olaf Seibert , freebsd-stable@freebsd.org, Jeremy Chadwick , John Baldwin , net@freebsd.org Subject: Re: mountd has resolving problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 20:49:06 -0000 On 2/17/2011 9:59 AM, Steven Hartland wrote: > ----- Original Message ----- From: "John Baldwin" >> Waiting for the default route to be pingable actually fixed a few >> other problems for us on 7 though as well (often ntpdate would not >> work on boot and now it works reliably, etc.) so we went with that route. > > Also fixed quite a few issues for us as well with services not reporting > properly. Definitely something that should be considered as part of core I've already said that I plan to commit this once the releases are done. :) Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/