Date: Fri, 17 Aug 2007 10:57:17 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Mike Makonnen <mtm@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc/rc.d Makefile lockd nfslocking statd Message-ID: <86vebeiln6.fsf@ds4.des.no> In-Reply-To: <200708170758.l7H7wRbV097007@repoman.freebsd.org> (Mike Makonnen's message of "Fri\, 17 Aug 2007 07\:58\:27 %2B0000 \(UTC\)") References: <200708170758.l7H7wRbV097007@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Makonnen <mtm@FreeBSD.org> writes: > Log: > The rc.d/nfslocking file controls two servers: rpc.statd and rpc.lockd.= It worked well > in most cases, except one. The 'restart' case was not working as expect= ed. Specifically, > it would stop both lockd and statd, but it would restart only statd (wh= ich appears first > in the script). This is because rc.subr(8) contains code to guard again= st infinite > recursion in the 'restart' casae. >=20=20=20 > To fix this use the traditional approach of controlling only one server= from one script by > breaking out rc.d/nfslocking into its contituent parts: rc.d/lockd and = rc.d/statd. Keep > rc.d/nfslocking around but don't include it in the boot rcorder(8)ing. Wouldn't it have been better to name them rpc_lockd and rpc_statd, to match their rc.conf variables? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86vebeiln6.fsf>