From owner-freebsd-current@FreeBSD.ORG Tue Mar 31 20:04:18 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8943E1065673 for ; Tue, 31 Mar 2009 20:04:18 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 009A28FC27 for ; Tue, 31 Mar 2009 20:04:17 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.2/8.14.2) with ESMTP id n2VK4Gs1077942; Tue, 31 Mar 2009 16:04:16 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.2/8.13.8/Submit) id n2VK4G9s077941; Tue, 31 Mar 2009 16:04:16 -0400 (EDT) (envelope-from wollman) Date: Tue, 31 Mar 2009 16:04:16 -0400 (EDT) From: Garrett Wollman Message-Id: <200903312004.n2VK4G9s077941@hergotha.csail.mit.edu> To: phk@phk.freebsd.dk X-Newsgroups: mit.lcs.mail.freebsd-current In-Reply-To: <96526.1238484035@critter.freebsd.dk> References: <49D1B261.6010406@FreeBSD.org> Organization: None X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Tue, 31 Mar 2009 16:04:16 -0400 (EDT) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hergotha.csail.mit.edu X-Mailman-Approved-At: Tue, 31 Mar 2009 20:47:30 +0000 Cc: current@freebsd.org Subject: Re: New rc.d/named features for testing: auto-forwarding and wait on boot 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: Tue, 31 Mar 2009 20:04:20 -0000 In article <96526.1238484035@critter.freebsd.dk>, phk@phk.freebsd.dk writes: >Maybe we need to do a more general mechanism, since many also >would like us to have confirmed the wall-clock-time via NTP before >we start anything that depends on it ? In my case, I needed something like this because ntpd can't resolve its servers until named is working, and if the resolution fails, ntpd simply gives up on those servers. The result is that ntpd starts with no associations configured and never synchronizes to anything. I'm not sure if this is fixed in more recent versions on ntpd. (I'm also dubious that you'd really want to wait 3*MINPOLL for ntpd to figure out what's going on before you finish booting, but that's more an argument to have with Dave Mills.) -GAWollman