Date: Sun, 3 Apr 2011 12:06:02 -0400 From: Ed Maste <emaste@freebsd.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Ed Maste <emaste@FreeBSD.org> Subject: Re: svn commit: r220153 - head/etc/rc.d Message-ID: <20110403160602.GA67576@sandvine.com> In-Reply-To: <alpine.BSF.2.00.1104031454260.6104@ai.fobar.qr> References: <201103300119.p2U1J18L046334@svn.freebsd.org> <alpine.BSF.2.00.1104031454260.6104@ai.fobar.qr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 03, 2011 at 02:56:50PM +0000, Bjoern A. Zeeb wrote:
> On Wed, 30 Mar 2011, Ed Maste wrote:
> > Replace ${SYSCTL_W} with ${SYSCTL} in rc.d scripts, as they are identical.
>
> ... for example OSX really requires the -w to alter a
> sysctl while we permit without. I thin kthe correct fix should have
> been to add a -w to SYSCTL_W.
NetBSD also requires -w as far as I know. However, we've deprecated the
switch -- see sysctl(8):
The -w option has been deprecated and is silently ignored.
I don't think there's much value in using a deprecated and ignored flag
in our startup scripts.
> That way one can grep for a read vs.
> write in the startup scrpits a lot more easily, etc.
Something along the lines of egrep -ir 'sysctl.*=' can be used to find
places that sysctls are written; this has the benefit of finding the
cases where we're already not using a ${SYSCTL} or ${SYSCTL_W} variable
today.
-Ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110403160602.GA67576>