From owner-freebsd-bugs Tue Oct 22 11:00:43 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19696 for bugs-outgoing; Tue, 22 Oct 1996 11:00:43 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA19689 for ; Tue, 22 Oct 1996 11:00:41 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA23161; Tue, 22 Oct 1996 12:00:22 -0600 (MDT) Date: Tue, 22 Oct 1996 12:00:22 -0600 (MDT) Message-Id: <199610221800.MAA23161@rocky.mt.sri.com> From: Nate Williams To: Heikki Suonsivu Cc: dg@Root.COM, freebsd-bugs@freefall.freebsd.org Subject: Re: bin/926 In-Reply-To: <199610221739.UAA13123@katiska.clinet.fi> References: <199610220842.BAA12410@freefall.freebsd.org> <199610221719.KAA25128@root.com> <199610221739.UAA13123@katiska.clinet.fi> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Heikki Suonsivu writes: > > David Greenman writes: > > >Synopsis: Mounting nfs disks before starting mountd: Chicken or Egg problem > > > >This is still valid problem; mountd is started in /etc/rc later than mount > > >-a -t nfs is run (checked current from two days ago). > > > > mountd is only needed to serve external mount requests for local > > filesystems that are being served. It is NOT needed to mount NFS disks on > > other servers. > > Please read the whole text; the problem is when two computers cross-mount > each other's disks. When they are rebooted at the same time and they > arrive to mount -a -t nfs they both block there to wait until other party > gets its mountd running, which of course never happens as mountd is started > after mount -a -t nfs. What we *really* need is documentation on the 'bg' option (background) which is on SunOS. This basically says attempt to mount the FS, but keep going if it doesn't happen. It's in the source, but not in the man-page. Nate