Date: Sun, 17 Jun 2018 21:22:57 +0100 From: Chris Rees <crees@bayofrum.net> To: freebsd-rc@freebsd.org Subject: Re: review of nfsd rc.d script patch Message-ID: <aacd4e3b-b8a1-5084-debc-402d7d9b4721@bayofrum.net> In-Reply-To: <YTOPR0101MB0953A6D3081676510290AEEFDD7C0@YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM> References: <YTOPR0101MB0953A6D3081676510290AEEFDD7C0@YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Rick, On 15/06/2018 21:53, Rick Macklem wrote: > Hi, > > For the pNFS service MDS machine, the nfsd can't be started until all nfs mounts > in /etc/fstab are done. > I think that adding "mountcritremote" to the "# REQUIRE:" line is sufficient to do this? > > I don't think delaying the startup of the nfsd daemon until after any NFS mounts > are done will do any harm, but if others think it would be a POLA violation, > I could make this dependent on the pNFS service being enabled. > Does anyone think this would cause a POLA violation? > > If someone familiar with the rc scripts could review this little patch, it would be > appreciated: > --- nfsd.old 2018-06-15 16:07:54.279786000 -0400 > +++ nfsd 2018-06-15 16:08:43.934603000 -0400 > @@ -4,7 +4,7 @@ > # > > # PROVIDE: nfsd > -# REQUIRE: mountd hostname gssd nfsuserd > +# REQUIRE: mountcritremote mountd hostname gssd nfsuserd > # KEYWORD: nojail shutdown > > . /etc/rc.subr Isn't this going to break local nfs mounts? Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aacd4e3b-b8a1-5084-debc-402d7d9b4721>