Date: Tue, 24 Oct 2000 18:17:56 -0400 From: Bill Vermillion <bill@bilver.wjv.com> To: freebsd-current@freebsd.org Subject: Re: new rc.network6 and rc.firewall6 Message-ID: <20001024181756.A2407@wjv.com> In-Reply-To: <21384.972424688@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Tue, Oct 24, 2000 at 02:58:08PM -0700 References: <imp@village.org> <21384.972424688@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 24, 2000 at 02:58:08PM -0700, Jordan Hubbard thus spoke: > > The scripts themselves have the ordering dependencies. The startup > > system runs them in the proper order. I don't know if this is > > pre-computed or redone each boot. > I'm really curious about this, myself. One of the reasons the SYSV > scripts have the numeric prefix is so that you know exactly what order > things will be started in. With the NetBSD stuff, this is not > immediately obvious though I guess one could have a top level rc file > with an explicit ordering similar to our various subdir Makefiles, > but that also gives you another location to edit when dropping > in a new startup file. This was my thought also. I put the TCP/IP scripts at 99 to make sure that any slow network initialization is done. Since they all start with S - for example S99tcp - moving it to s99tcp will keep it from starting, and the Knn<name> in the same directory is used to stop things when moving from that run level. It's one of the things I like about the Sys V /etc/rc<n>.d directory structure, as you can easily fine tune it to fit your needs. Just a look at the files and you know the order. Bill -- Bill Vermillion - bv @ wjv . com -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001024181756.A2407>