Date: Tue, 13 Jan 2004 10:59:31 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: ngctl and rc.conf Message-ID: <20040113165931.GN66765@seekingfire.com> In-Reply-To: <44u130lg73.fsf@be-well.ilk.org> References: <20040112221218.GI66765@seekingfire.com> <44u130lg73.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 12, 2004 at 09:45:20PM -0500, Lowell Gilbert wrote: > Tillman Hodgson <tillman@seekingfire.com> writes: > > > Howdy folks, > > > > What's the best way to build ng_one2many interfaces into rc.conf such > > that they're brought up (live) at the "normal" time so that: > > > > 1) configuration remains centralized in rc.conf > > 2) other pieces that depend on a network being present don't fail in > > enlightening ways? > > > > I want to avoid the "make a shell script in /usr/local/etc/rc.d" > > approach. > > Nobody else has written this shell script for you, so you can't just > configure it in rc.conf and turn it on. If you want, you can add it > to rc.network and submit the patches in a PR, so future upgrades will > include it. I'll play around with it and see what I can come up with -- at first blush it doesn't look difficult, just time-consuming to ensure that it fails gracefully under misconfiguration. -T -- "Seeing yourself as you want to be is the key to personal growth." - Unknown
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040113165931.GN66765>