From owner-freebsd-hackers Fri Sep 12 23:54:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA09868 for hackers-outgoing; Fri, 12 Sep 1997 23:54:13 -0700 (PDT) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA09862 for ; Fri, 12 Sep 1997 23:54:06 -0700 (PDT) Received: (from fn@localhost) by trinity.radio-do.de (8.8.7/8.8.5/RADIO-1.1) id IAA06467; Sat, 13 Sep 1997 08:53:24 +0200 (CEST) To: Doug White Cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: nfs startup - perhaps it is a problem References: From: Frank Nobis Date: 13 Sep 1997 08:53:22 +0200 In-Reply-To: Doug White's message of Fri, 12 Sep 1997 22:35:05 -0700 (PDT) Message-ID: Lines: 47 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Doug White writes: > On Mon, 8 Sep 1997, Brian Somers wrote: > > > The problem was that mount couldn't resolve the host names from > > fstab. This brings up two things: > > Oh that doesn't help ;-) > > > 1. Why is "mount -a -t nfs" redirected to /dev/null ? It seems > > happy if there are no nfs filesystems in fstab, so wouldn't it be > > better if we see any such errors ? > > > > 2. Should named be done in pass 1, or is it done this way because > > your named config files may be on an nfs drive ;-/ > > > > The whole thing is worked around nicely by putting a nameserver in > > resolv.conf or by reading /etc/hosts first and putting all your "close > > friends" in there. I think 1. should be done at least. > The order of host.conf should not matter for a client machine, which is not the primary nameserver for a particular domain. I have ´bind´ and than ´hosts´ in my host.conf. So I will ask the nameserver running on an other machine Whenn that fails, I try the backup in hosts. But all that doesn´t prevent one from a long,long wait nfs-mounting some remote filesystem, when the fileserver is not responding. I have changed the nfs call to that: echo -n 'mounting remote nfs filesystems' mount -a -t nfs -o bg echo "." In my setup there are at least three hosts which share their local partitions to each other. It is not unlikely that one of them is down, when I reboot. With the background option the mount doesn´t hang the system. I know that setups exists, where it makes no sense to continue on nfs mount failure, but that doesn´t count for me. Just my 2p. -- Frank Nobis Email: PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by FreeBSD Fax: +49 231 7213816