Date: Wed, 17 Sep 1997 00:48:04 +0100 From: Brian Somers <brian@awfulhak.org> To: Greg Lehey <grog@lemis.com> Cc: Brian Somers <brian@awfulhak.org>, freebsd-questions@FreeBSD.ORG, FreeBSD Hackers <hackers@FreeBSD.ORG> Subject: Re: nfs startup Message-ID: <199709162348.AAA22852@awfulhak.demon.co.uk> In-Reply-To: Your message of "Tue, 16 Sep 1997 10:59:40 %2B0930." <19970916105940.15713@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Thu, Sep 04, 1997 at 11:31:48PM +0100, Brian Somers wrote:
> > This has to be a dumb question, but I can't fathom it.
> >
> > /etc/rc sources /etc/rc.network and then runs network_pass1.
> > Directly afterwards, it runs ``mount -a -t nfs''.
> >
> > However, network_pass3 (invoked much later) starts nfsiod along with
> > the other nfs stuff.
>
> You don't need nfsiod for mounting, but you do need to resolve the
> names. If you're running a name server, I don't think it's reasonable
> to expect an /etc/hosts entry for each system you're mounting NFS file
> systems from. Unfortunately, named doesn't get started until
> network_pass2, so this can't work in a name server environment.
>
> Here's a suggested patch:
[.....]
But what about starting named in network_pass1 ?
> The & after the mount command is to let it continue to try to mount
> file systems on systems which are not currently up; otherwise system
> startup will hang at this point. As you see, I also agree with the
> sentiment that the messages should be seen.
I've already removed the /dev/null bit, and agree that the & is a
good idea too.
> Greg
--
Brian <brian@awfulhak.org>, <brian@freebsd.org>, <bri@openbsd.org>
<http://www.awfulhak.org>;
Don't _EVER_ lose your sense of humour....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709162348.AAA22852>