From owner-freebsd-questions@FreeBSD.ORG Tue Jul 24 16:32:41 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CB4016A419 for ; Tue, 24 Jul 2007 16:32:41 +0000 (UTC) (envelope-from chris@vindaloo.com) Received: from corellia.vindaloo.com (corellia.vindaloo.com [64.51.148.100]) by mx1.freebsd.org (Postfix) with ESMTP id 4944213C4E5 for ; Tue, 24 Jul 2007 16:32:41 +0000 (UTC) (envelope-from chris@vindaloo.com) Received: from dagobah.vindaloo.com (dagobah.vindaloo.com [172.24.145.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by corellia.vindaloo.com (Postfix) with ESMTP id 72E655CA2; Tue, 24 Jul 2007 12:15:22 -0400 (EDT) Received: from localhost.vindaloo.com (localhost.vindaloo.com [IPv6:::1]) by dagobah.vindaloo.com (8.13.8/8.13.8) with ESMTP id l6OGEEcs002430; Tue, 24 Jul 2007 12:14:14 -0400 (EDT) (envelope-from chris@vindaloo.com) From: Christopher Sean Hilton To: Reid Linnemann In-Reply-To: <469B7CE3.5040305@cs.okstate.edu> References: <4697FCCA.5010802@tundraware.com> <469B7CE3.5040305@cs.okstate.edu> Content-Type: text/plain Date: Tue, 24 Jul 2007 12:14:13 -0400 Message-Id: <1185293653.2229.2.camel@dagobah.vindaloo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: tundra@tundraware.com, FreeBSD Mailing List Subject: Re: named and nfs mounts at boot time X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2007 16:32:41 -0000 On Mon, 2007-07-16 at 09:12 -0500, Reid Linnemann wrote: > Written by Tim Daneliuk on 07/13/07 17:29>> > > > > 'Just wondering if there is a way to get the warnings during boot to > > be quiet without resorting to using IP addresses in the fstab nfs > > mount entries... > > > > > If the filesystems are not needed until the system is up multiuser, you > could specify the 'late' option on them in fstab, forcing them to be > delayed until /etc/rc.d/mountlate is run after /etc/rc.d/DAEMON has > completed. This will ensure that named is running prior to the mount, > since DAEMON requires SERVERS, which starts named. It seems like a lot of work but the automounting daemon amd solves these and other issues with an nfs server being unavailable when an nfs client boots up. -- Chris -- __o "All I was doing was trying to get home from work." _`\<,_ -Rosa Parks ___(*)/_(*)___________________________________________________________ Christopher Sean Hilton pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14