Date: Thu, 7 Oct 2010 07:42:42 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: "Douglas K. Rand" <rand@meridian-enviro.com> Cc: freebsd-hackers@freebsd.org Subject: Re: sysrc -- a sysctl(8)-like utility for managing /etc/rc.conf et. al. Message-ID: <alpine.BSF.2.00.1010070737301.3725@wonkity.com> In-Reply-To: <87fwwici02.wl%rand@meridian-enviro.com> References: <1286397912.27308.40.camel@localhost.localdomain> <AANLkTikoohMo5ng-RM3tctTH__P6cqhQpm=FPhSE9mMg@mail.gmail.com> <51B4504F-5AA4-47C5-BF23-FA51DE5BC8C8@vicor.com> <4CAD513F.3010903@DataIX.net> <D5D9B585-96DA-4BD0-899D-A7BFFC0C540C@vicor.com> <4CAD7563.1070706@DataIX.net> <87fwwici02.wl%rand@meridian-enviro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 7 Oct 2010, Douglas K. Rand wrote: > I think that this script might also fill a void with using Puppet as a > configuration tool. Currently Puppet, as its default behaviour, uses > files in /etc/rc.conf.d to set variables. I've found this approach > really lacking because you cannot do things like: > > nfs_server_enable="YES" > > via a /etc/rc.conf.d file because multiple things (like lockd, mountd, > nfsd, nfsserver, and statd) all need nfs_server_enable set, as one > example. This script would provide an easy method for puppet to "edit" > lines in /etc/rc.conf. Consider also the docs that tell the user to echo 'something_enable="YES"' >> /etc/rc.conf which can produce duplicate and possibly differing entries. Or non-working entries if there was no ending \n present, or even a broken rc.conf that breaks startup.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1010070737301.3725>