Date: Mon, 9 May 2011 14:02:44 -0400 From: Jason Hellenthal <jhell@DataIX.net> To: Gordon Tetlow <gordon@tetlows.org> Cc: freebsd-rc@freebsd.org Subject: Re: [RFC][Change-Request] Create usefulness in rc.subr etc/rc.conf.d/*.conf namespace. Message-ID: <20110509180243.GA82456@DataIX.net> In-Reply-To: <BANLkTin%2BtgJqM8OmH%2BtiFsiUKPsdOj921w@mail.gmail.com> References: <20110508191336.GC3527@DataIX.net> <BANLkTi=hozQBLUC15NsF2rky2OfFW=t_RQ@mail.gmail.com> <20110509134617.GA28036@DataIX.net> <BANLkTin%2BtgJqM8OmH%2BtiFsiUKPsdOj921w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Gordon, On Mon, May 09, 2011 at 10:19:50AM -0700, Gordon Tetlow wrote: > On Mon, May 9, 2011 at 6:46 AM, Jason Hellenthal <jhell@dataix.net> wrote: > > Dump you rc.conf to two place. home-lan.conf and away-lan.conf and use > > chmod to turn one or the other off. You can still have a global set of > > services enabled in rc.conf but still be able to choose a way for them = to > > act by adding the _flags or even _enable rc_vars to each. > > > > Since this processes after rc.conf* you could treat those config's as j= ust > > modifiers to get a certain behavior as they override what is in rc.conf* > > in the same way that rc.conf overrides etc/defaults/rc.conf. How you na= me > > them can clearly depict what it does as well. This is one reason why I > > mainly went with adding the -x bit because these can coexist with a full > > rc.conf but be changed quickly when you want a certain behavior. >=20 > For everything else in the proposal, I feel the use of the execute bit > is incorrect. Nowhere else in the system is there a precedent of using > the execute bit to toggle on and off a configuration file. You can no > longer do a simple 'grep foo_enable *.conf' and see which active files > have that set. I would prefer to use the pattern established by many > 3rd parties and use the convention that you may mv the file out of the > way so it no longer matches the *.conf glob. Something like 'mv > foo.conf foo.conf.disable' is unambiguous and can easily be searched > with a simple ls or grep command. Using the execute bit is less > transparent, unprecedented, and confusing. >=20 Ok, I do agree with you on this. There is another route that I propose the= =20 same type of thing but in the style or sense of a lockfile. Not that it=20 actually locks anything but would make it visable enough to where it can=20 be disabled in-place rather than moved around. It would act similiar to this in shell: if [ -f $_modular_conf -a ! -f $_modular_conf.disable ]; then [...] Then to disable one config someone can still do so without cp/mv and just= =20 touch or rm /etc/rc.conf.d/my-conf.conf.disable How does that sound to you ? and everyone else ? --=20 Regards, (jhell) Jason Hellenthal --AqsLC8rIMeq19msA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJNyCxDAAoJEJBXh4mJ2FR+/N0H/i4D8VNLGeA1ustIFPYoY1E9 A48N8wBXHAe+kiib2PZmbgIcLddHxm83Mq9qX+yWCSfgj4gcptewb582JlrU0ULM 1QreyrH3oSKZaVLLyxMxMDr0OlHWugMxjgjb6mSBWTEaoRAtg2aqO+mXw5IzTZWk /keY0WADnT14wL33HmHc/74wZzqYO5sVoh4J6L5u1syy6xeuSwJ8DMt28MZnflkV KfEB9SJysg2384wmuSpnxBll1lNDWU15zeYcnb6JAHLY6ybQoYJxfT3r1GNLmGID CSVj9Jg9Un/fh2JMAuL+1S6NVubeGAPQyd1CO/qYaCB3zqntrOVTh4Axv8Zw/4k= =xe9T -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110509180243.GA82456>