Date: Tue, 31 Aug 2010 11:31:58 -0700 From: Sean Bruno <seanbru@yahoo-inc.com> To: Dirk-WIllem van Gulik <dirkx@webweaving.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "sbruno@freebsd.org" <sbruno@freebsd.org>, Scott Long <scottl@samsco.org> Subject: Re: /etc/rc.d/mountcritremote Message-ID: <1283279518.3665.64.camel@home-yahoo> In-Reply-To: <F6A6C8FF-911E-4A32-B4BC-1289D48EC655@webweaving.org> References: <1283271393.3665.13.camel@home-yahoo> <F6A6C8FF-911E-4A32-B4BC-1289D48EC655@webweaving.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2010-08-31 at 10:45 -0700, Dirk-WIllem van Gulik wrote: > On 31 Aug 2010, at 17:16, Sean Bruno wrote: > > > An issue in testing came up where we were trying to mount NFS > > directories from the same server, i.e. a machine trying to mount an NFS > > dir on itself. > > > > Because mountcritremote runs before the NFS server is up, we modified > > the REQUIRES section and appended nfsd. > > Are you sure that is right for PXE style boots - where this is heavily relied on ? > > Dw. Not sure. If the nfs server isn't configured to startup, then this is a no-op. I'm not sure what application would be running in a pxeboot environment and run an NFS server. Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1283279518.3665.64.camel>