You don't need an rc.local script. If you look in /etc/rc2.d/ you'll see lots of S<number><name> scripts. These are the scripts that get run when you start the system. The 'S' is for "Start" (I guess), and there are "K" scripts for "Kill" in other related directories. The number is the order in which it will run 00 is first, 99 is last. These files are symbolic links to files in the /etc/init.d/ directory. There are two files that would be in your /etc/init.d if you installed the networking and apache packages (which you should, the package management is debian's best feature): networking and apache. If they're not there, make up your own and symlink them to /etc/rc2.d. Or if you install the packages ifupdown, net-tools, and netbase (which you might have), you'll have the networking script built for you, and you just add your settings to the /etc/network/interfaces file.
If you do build your own, it's best to put one set of related startup commands in one file, so you can bring that daemon up or down, without interfering with others. On Thu, Aug 23, 2001 at 05:19:19PM -0700, bob parker scribbled... > I'm still quite new to this excellent os (Potato r3) > and am building a web server. > I have made a script - rc.local to configure my > network adapter using ifconfig and route. > At the moment I'm invoking this by hand after bootup. > My question is where do I install this script so that > it's automatically run on boot up? > > I'm also running Apache by hand, having built it from > a tarball off a magazine CD. That's what the boss > wanted!. Should I start that from inside the rc.local > script? > > Thanks > Bob Parker
