From owner-freebsd-rc@freebsd.org Sun Jun 17 20:40:34 2018 Return-Path: Delivered-To: freebsd-rc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E47C81009197 for ; Sun, 17 Jun 2018 20:40:33 +0000 (UTC) (envelope-from crees@bayofrum.net) Received: from mail92c50.megamailservers.eu (mail170c50.megamailservers.eu [91.136.10.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 589A97DF4A for ; Sun, 17 Jun 2018 20:40:33 +0000 (UTC) (envelope-from crees@bayofrum.net) X-Authenticated-User: bayofrum@uwclub.net Received: from pegasus.bayofrum.net (81-178-234-191.dsl.pipex.com [81.178.234.191]) (authenticated bits=0) by mail92c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id w5HKN1Uk012440 for ; Sun, 17 Jun 2018 20:23:02 +0000 Received: from [192.168.1.121] (POSEIDON.bayofrum.net [192.168.1.121]) by pegasus.bayofrum.net (Postfix) with ESMTPSA id 6069B81541 for ; Sun, 17 Jun 2018 21:22:59 +0100 (BST) Subject: Re: review of nfsd rc.d script patch To: freebsd-rc@freebsd.org References: From: Chris Rees Openpgp: preference=signencrypt Message-ID: Date: Sun, 17 Jun 2018 21:22:57 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-GB X-bayofrum-MailScanner-Information: Please contact the ISP for more information X-bayofrum-MailScanner-ID: 6069B81541.A6E48 X-bayofrum-MailScanner: Found to be clean X-bayofrum-MailScanner-From: crees@bayofrum.net X-Spam-Status: No X-CTCH-RefID: str=0001.0A0B0206.5B26C326.009D, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.3 cv=TO5rtWta c=1 sm=1 tr=0 a=3/mv0xAtjE5S4uD53Yf/JA==:117 a=3/mv0xAtjE5S4uD53Yf/JA==:17 a=IkcTkHD0fZMA:10 a=7mUfYlMuFuIA:10 a=kHsINHuQoMkJq8ekQtMA:9 a=QEXdDO2ut3YA:10 X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 20:40:34 -0000 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.