Date: Tue, 12 Jul 2016 15:50:53 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-current@freebsd.org Subject: Re: Oversight in /etc/defaults/rc.conf Message-ID: <20160712155053.6b5a0d99@gumby.homeunix.com> In-Reply-To: <483d186c-ca63-60ef-5703-8a7ae37e9ced@freebsd.org> References: <f41405cb-bb41-e8f7-74eb-3dda5e3ed550@FreeBSD.org> <20160712122732.GA5596@FreeBSD.org> <483d186c-ca63-60ef-5703-8a7ae37e9ced@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Jul 2016 15:10:43 +0100 Matthew Seaman wrote: > I'm not religious about it being turned off per se. More that it > should have a clearly defined on/off state shown in the defaults. > > I went for 'off' following the general principle that rc.conf items > should mostly be off by default and require specific action to enable. > Yes, there are exceptions to this rule, but I see no particular reason > that iovctl should be one. What's the advantage to turning it on by > default on every FreeBSD installation? Unless I'm misunderstanding the situation. rc.d/iovctl isn't actually doing anything by default because of iovctl_files="". There is an analogy with rc.d/sysctl which runs by default, with a an empty sysctl.conf file. This also has no explicit enable entry in rc.conf.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160712155053.6b5a0d99>