Date: Mon, 20 Jun 2011 09:45:42 -0700 From: "Devin Teske" <dteske@vicor.com> To: <swehack@gmail.com>, "'Mark Blackman'" <mark@exonetric.com> Cc: freebsd-rc@freebsd.org Subject: RE: Status of /etc/rc.conf.d/servicename feature in rc.subr Message-ID: <00fb01cc2f69$7f493f00$7ddbbd00$@vicor.com> In-Reply-To: <BANLkTimUW6bhsGae4sXvQqMH7xWJreDsog@mail.gmail.com> References: <BANLkTimmVTjA1Dkm-hMz7ZMEsGNBSxm4kA@mail.gmail.com> <8373928E-23AF-41D1-83BA-34324C38BB02@exonetric.com> <BANLkTimWpmHdqqQxPVENp=yw5KoEu_ggZA@mail.gmail.com> <BANLkTimUW6bhsGae4sXvQqMH7xWJreDsog@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-rc@freebsd.org [mailto:owner-freebsd-rc@freebsd.org] > On Behalf Of Stefan Midjich > Sent: Monday, June 20, 2011 2:15 AM > To: Mark Blackman > Cc: freebsd-rc@freebsd.org > Subject: Re: Status of /etc/rc.conf.d/servicename feature in rc.subr >=20 > Actually I have something to add about /etc/rc.conf.d and it's not about = the shell > code. >=20 > My purpose to all this was to find a way to configure network interfaces = that > doesn't require parsing rc.conf. I've written a utility named sysrc(8) that works like sysctl(8), making management of rc.conf(5) trivial. http://druidbsd.sourceforge.net/download/sysrc.txt Quite a few people have written to me to say thanks, that it makes automati= on and mass-deployment much simpler (extensively supports jails too). --=20 Devin > We deploy hundreds of machines using data > center management tools so writing functions in these tools for network > configuration becomes much easier if you separate the network configurati= on > into their own files. >=20 > So using /etc/rc.conf.d/network will work, but I would like to go further= and > suggest the OpenBSD model of using interface.ifname or something similar.= One > file for each interface that is. >=20 > 2011/6/20 Stefan Midjich <swehack@gmail.com>: > > Shortly after I posted my e-mail I was talking about this with a > > co-worker and realized that I'm using the wrong servicename in > > rc.conf.d. Checking the name variable in /etc/rc.d/netif made it all > > much more clear. > > > > And yes I would support the further development of this feature > > because I plan on using it in deployment of FreeBSD nodes. > > > > 2011/6/20 Mark Blackman <mark@exonetric.com>: > >> On 20 Jun 2011, at 09:20, Stefan Midjich wrote: > >> > >>> I noticed in /etc/rc.subr that the function load_rc_config sources > >>> /etc/rc.conf.d/${_name}. This is however undocumented, NetBSD > >>> mentions this feature in rc.conf(5) but FreeBSD does not. > >>> > >>> I have two questions, is this a new undocumented feature, or an old > >>> one being phased out? I'm hoping it's a new because I really want > >>> this feature. > >>> > >>> Second question, how do I use it? I've tried to track the ${_name} > >>> variable but I can't find anyone calling the parent function > >>> load_rc_config_var() where the name variable is set from its first > >>> argument. > >> > >> I've added a file called 'jail' there =A0and /etc/rc.d/jail will then > >> pick up configuration data from /etc/rc.conf.d/jail. > >> > >> I think it's quite a useful feature and would support it's continued > >> existence. However I wonder who else might be interested in a better > >> referencing method more like a perl hash or YAML files for the > >> configuration data. > >> > >> There's a clear nesting behaviour there built from shell variable > >> names that I find a little bit overextended. > >> > >> - Mark > >> > > > > > > > > -- > > > > > > Med v=E4nliga h=E4lsningar / With kind regards > > > > Stefan Midjich > > http://swehack.se > > >=20 >=20 >=20 > -- >=20 >=20 > Med v=E4nliga h=E4lsningar / With kind regards >=20 > Stefan Midjich > http://swehack.se > _______________________________________________ > freebsd-rc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-rc > To unsubscribe, send any mail to "freebsd-rc-unsubscribe@freebsd.org" _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. _____________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00fb01cc2f69$7f493f00$7ddbbd00$>