Date: Tue, 12 Jul 2016 11:26:54 -0400 From: Ryan Stone <rysto32@gmail.com> To: RW <rwmaillists@googlemail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Oversight in /etc/defaults/rc.conf Message-ID: <CAFMmRNzTYGyM-NOfqfFru5pnRuwBS0Vf4GB_m9vHKi0=HDKMLA@mail.gmail.com> In-Reply-To: <20160712155053.6b5a0d99@gumby.homeunix.com> References: <f41405cb-bb41-e8f7-74eb-3dda5e3ed550@FreeBSD.org> <20160712122732.GA5596@FreeBSD.org> <483d186c-ca63-60ef-5703-8a7ae37e9ced@freebsd.org> <20160712155053.6b5a0d99@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 12, 2016 at 10:50 AM, RW <rwmaillists@googlemail.com> wrote: > 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. > That is how it is intended to work, and rc.d/sysctl was the inspiration for that script if memory serves. I'm not entirely opposed to an iovctl_enable variable but it seems redundant.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNzTYGyM-NOfqfFru5pnRuwBS0Vf4GB_m9vHKi0=HDKMLA>