Date: Fri, 15 Jun 2018 20:53:52 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: "rc@freebsd.org" <rc@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: review of nfsd rc.d script patch Message-ID: <YTOPR0101MB0953A6D3081676510290AEEFDD7C0@YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM>
next in thread | raw e-mail | index | archive | help
Hi, For the pNFS service MDS machine, the nfsd can't be started until all nfs m= ounts in /etc/fstab are done. I think that adding "mountcritremote" to the "# REQUIRE:" line is sufficien= t to do this? I don't think delaying the startup of the nfsd daemon until after any NFS m= ounts 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 @@ # =20 # PROVIDE: nfsd -# REQUIRE: mountd hostname gssd nfsuserd +# REQUIRE: mountcritremote mountd hostname gssd nfsuserd # KEYWORD: nojail shutdown =20 . /etc/rc.subr Thanks, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTOPR0101MB0953A6D3081676510290AEEFDD7C0>