From owner-freebsd-bugs  Tue Oct 22 12:50:19 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA26230
          for bugs-outgoing; Tue, 22 Oct 1996 12:50:19 -0700 (PDT)
Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.16])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA26182;
          Tue, 22 Oct 1996 12:50:00 -0700 (PDT)
Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.7.5/8.7.3) id VAA14062; Tue, 22 Oct 1996 21:47:08 +0200 (MET DST)
From: Robert Eckardt <roberte@mep.ruhr-uni-bochum.de>
Message-Id: <199610221947.VAA14062@ghost.mep.ruhr-uni-bochum.de>
Subject: Re: bin/926
In-Reply-To: <199610221624.TAA05589@katiska.clinet.fi> from Heikki Suonsivu at "22. Oct. 96 19:23:15"
To: hsu@clinet.fi (Heikki Suonsivu)
Date: Tue, 22 Oct 1996 21:47:07 +0200 (MET DST)
Cc: roberte@mep.ruhr-uni-bochum.de, scrappy@freefall.freebsd.org,
        hsu@clinet.fi, freebsd-bugs@freefall.freebsd.org
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Robert Eckardt writes:
>  > > Synopsis: Mounting nfs disks before starting mountd: Chicken or Egg probl
em
[...]
>  > > This is still valid problem; mountd is started in /etc/rc later than moun
t
>  > > -a -t nfs is run (checked current from two days ago).
>  >
>  > This is no conflict. mountd is needed for the NFS-Server.
>  > Mounting NFS-FSs is done by the NFS-Client, which needs only nfsiod.
>
> The PR was about two machines mounting each others disks.  If both panic or
> are rebooted at the same time, they both lock up waiting for each other
> coming up.

Sorry, I hadn't the full PR.
For me it never counted, since I'm using the bg option on nfs mounts,
so I have no problems when X-mounting.

I think the idea putting it as early as possible in rc was that one
can put as much as possible on some nfs server (which should of 
course be up :-).

So, may be it's a good solution is to document `bg' AND move `mount -t nfs'
past mountd as you suggested.
(I can think only of rare cases where people would like to put these
daemons on external disks -- and these admins should know how to fix it.)

Robert

> if [ "X${nfs_client}" = X"YES" ]; then
>         echo -n ' nfsiod';              nfsiod -n 4
> fi
> 
> mount -a -t nfs >/dev/null 2>&1
> 
> if [ "X${amdflags}" != X"NO" ]; then
>         echo -n ' amd';                 amd ${amdflags}
> fi
> 
> -- 
> Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi
> mobile +358-40-5519679 work +358-0-43542270 fax -4555276

-- 
Robert Eckardt                \\ FreeBSD -- solutions for a large universe.(tm)
RobertE@MEP.Ruhr-Uni-Bochum.de \\       What do you want to boot tomorrow ?(tm)
http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte
For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de