Date: Wed, 17 Sep 1997 09:45:59 +0930 From: Greg Lehey <grog@lemis.com> To: Brian Somers <brian@awfulhak.org> Cc: freebsd-questions@FreeBSD.ORG, FreeBSD Hackers <hackers@FreeBSD.ORG> Subject: Re: nfs startup Message-ID: <19970917094559.47017@lemis.com> In-Reply-To: <199709162348.AAA22852@awfulhak.demon.co.uk>; from Brian Somers on Wed, Sep 17, 1997 at 12:48:04AM %2B0100 References: <19970916105940.15713@lemis.com> <199709162348.AAA22852@awfulhak.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 17, 1997 at 12:48:04AM +0100, Brian Somers wrote: >> 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 ? If you like. I thought one was about as good as the other, but starting named earlier might forestall other potential hang conditions. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970917094559.47017>