Date: Tue, 22 Oct 1996 16:48:21 -0400 (EDT) From: "Marc G. Fournier" <scrappy@ki.net> To: Heikki Suonsivu <hsu@clinet.fi> Cc: Robert Eckardt <roberte@mep.ruhr-uni-bochum.de>, "Marc G. Fournier" <scrappy@freefall.freebsd.org>, freebsd-bugs@freefall.freebsd.org Subject: Re: bin/926 Message-ID: <Pine.NEB.3.95.961022164637.284B-100000@quagmire.ki.net> In-Reply-To: <199610221624.TAA05589@katiska.clinet.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Oct 1996, Heikki Suonsivu wrote:
> > > Synopsis: Mounting nfs disks before starting mountd: Chicken or Egg problem
> 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.
>
> I have moved mountd startup in /etc/rc like this:
>
> # $rwhod is imported from /etc/sysconfig;
> # if $rwhod is set to YES, rwhod is run.
> if [ "X${rwhod}" = X"YES" ]; then
> echo -n ' rwhod'; rwhod
> fi
>
> if [ "X${nfs_server}" = X"YES" -a -r /etc/exports ]; then
> echo -n ' mountd'
> if [ "X${pcnfsd}" = X"YES" ]; then
> mountd -n
> else
> mountd
> fi
> echo -n ' nfsd'; nfsd -u -t 4
> fi
>
> 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
>
Is there any reacon why the above order is a bad idea? Both
mountd/nfsd are in /sbin, which I don't believe *should* ever be nfs
mount'd, and therefore should have any reason for needing to wait for
the nfs drives to be mounted...
Marc G. Fournier scrappy@ki.net
Systems Administrator @ ki.net scrappy@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.961022164637.284B-100000>