From owner-freebsd-questions@FreeBSD.ORG Fri Jul 13 22:29:44 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 121FC16A408 for ; Fri, 13 Jul 2007 22:29:44 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from eskimo.tundraware.com (eskimo.tundraware.com [66.92.130.161]) by mx1.freebsd.org (Postfix) with ESMTP id C5E4413C481 for ; Fri, 13 Jul 2007 22:29:43 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (ozzie.tundraware.com [66.92.130.199]) (authenticated bits=0) by eskimo.tundraware.com (8.14.1/8.14.1) with ESMTP id l6DMTZsK098948 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Jul 2007 17:29:36 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4697FCCA.5010802@tundraware.com> Date: Fri, 13 Jul 2007 17:29:30 -0500 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: FreeBSD Mailing List Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-tundraware.com-MailScanner-Information: Please contact the ISP for more information X-tundraware.com-MailScanner: Found to be clean X-tundraware.com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 1, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-tundraware.com-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: named and nfs mounts at boot time X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tundra@tundraware.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2007 22:29:44 -0000 While we're on the subject of dns ... I have nfs mounts configured in /etc/fstab using the host *name*. When the system boots, it grumbles about the name resolution because named has not yet been started. It works fine because, by the time you have a fully booted system, named is running and nfs runs happily. '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... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/