From owner-freebsd-hackers Sun Aug 25 23:54:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23400 for hackers-outgoing; Sun, 25 Aug 1996 23:54:22 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA23377 for ; Sun, 25 Aug 1996 23:54:19 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id IAA00880 for ; Mon, 26 Aug 1996 08:53:47 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma000815; Mon Aug 26 08:53:09 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id IAA24052 for ; Mon, 26 Aug 1996 08:55:51 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-1.2a-960822) with ESMTP id IAA29078 for ; Mon, 26 Aug 1996 08:54:35 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 26 Aug 96 08:54:39 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 26 Aug 96 08:54:22 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: freebsd-hackers@freebsd.org Date: Mon, 26 Aug 1996 08:54:15 GMT+0100 Subject: Re: NFS and the nameserver... Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail v3.22 Message-ID: <49448A3432@NLNMG01.nym.sc.philips.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Datum verzending: Fri, 16 Aug 1996 11:58:32 -0400 (EDT) > Van: Thomas David Rivers > Aan: ponds!mt.sri.com!nate@freefall.freebsd.org > Onderwerp: Re: NFS and the nameserver... > kopieen naar: ponds!freefall.cdrom.com!freebsd-hackers@freefall.freebsd.org > > > We need a small change to /etc/rc. > > > > And I assume you've made that change. :) > > > > > I discovered this when I set up a primary nameserver on a machine > > > that also wanted to mount NFS mount points. > > > > > > If you have an /etc/resolv.conf, and you are the primary name > > > server. The > > > > > > mount -a -t nfs > > > > > > in /etc/rc happens _before_ named is started. This means that > > > the mounts fail (timing out eventually). > > > > > > I think it would be prudent to move the > > > > > > mount -a -t -nfs > > > > > > command until after all the networking deamons have begun, but > > > particularly after named has started. > > > > Except that some of the networking daemons live in /usr, which must > > mounted on many boxes which boot diskless and/or mount /usr alone. > > > > There is no 'perfect' solution to where the NFS mount commands go, and > > it was determined that the current position is the 'best' for most > > people. If it doesn't work for your installation, move it (which you've > > done already). > > > > > > > > Nate > > > > Well - yes, err..., umm... I made that change. > > Seems like a simple 'if' is appropriate here. You could > set up a sysconfig parm, i.e. "diskless" and do the NFS > mounts early if this is a diskless machine. > > if [ ! X"$diskless" = X"NO" ] > then > mount -a -t nfs > NFS_mounted=yes > fi > > .... > > > after named, etc... > > if [ ! "NFS_mounted" = "yes" ] > then > mount -a -t nfs > fi > > > also - another clever trick is to put the mount command early > in /etc/rc and simply run it in the background. Then, it's likely > that the nameserver will get "cranked up" before the timeout > and the mounts will succeed... > I don't like the sound of that "likely". Does this mean that with the new sysconfig my system will be "likely" to boot correctly? Groetjes, Kees Jan