Date: Fri, 24 Jun 2005 04:54:27 +0300 From: Abu Khaled <khaled.abu@gmail.com> To: Reid Linnemann <lreid@cs.okstate.edu> Cc: freebsd-questions@freebsd.org Subject: Re: netgraph startup Message-ID: <a64c109e05062318541aaa7fb8@mail.gmail.com> In-Reply-To: <20050623155015.CC6F0A0633@csa.cs.okstate.edu> References: <20050623155015.CC6F0A0633@csa.cs.okstate.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/23/05, Reid Linnemann <lreid@cs.okstate.edu> wrote: >=20 > I'm using netgraph to bridge a few interfaces on a -CURRENT system. > I've used the example bridge script > /usr/share/examples/netgraph/ether.bridge, and it works perfectly after > setting the interface vars. >=20 > However, there are no rc.d hooks (that I am aware of) that will kick off > netgraph scripts on system boot, forcing me to manually run the netgraph > script at each reboot. I'm sure I could hack the script to give it > rcorder keywords and handlers for rcng arguments, but that seems to be > an overworked solution. I'm curious, how have other netgraph users have > solved this problem? Why don't you start your script from /etc/rc.local. I use rc.local to start many scripts for custom commands/daemons I need to be ready once the system (re)starts. # ee /etc/rc.local <path to script>/foo.sh --=20 Kind regards Abu Khaled
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a64c109e05062318541aaa7fb8>