Re: Proper place for IPCHAINS rules

[Brian Servis <servis@purdue.edu>]

*- On 15 Nov, Bryan Scaringe wrote about "Re: Proper place for IPCHAINS rules"
> Thanks,
>         Just out of curiosity, when in the boot process are the
> scripts in /etc/rc.boot executed?
> 

Note: The /etc/rc.boot directory is obsolete in the potato release. It
is replaced by the /etc/rcS.d directory.  See the man page for rc.boot
in slink or potato.

The /etc/rcS.d directory is read before the runlevel scripts are run
and it is only run once per boot.  See the README.runlevels.gz file in
the sysvinit doc directory.  Primarily you will find:

1. Boot.

   When the systems boots, the /etc/init.d/rcS script is executed. It
   in turn executes all the S* scripts in /etc/rcS.d in alphabetical
   (and thus numerical) order. The first argument passed to the
   executed scripts is "start". The runlevel at this point is "N" (none).

   Only things that need to be run once to get the system in a consistent
   state are to be run. The rcS.d directory is NOT ment to replace rc.local.
   One should not start daemons in this runlevel unless absolutely
   nessecary. Eg, NFS might need the portmapper, so it is OK to start it
   early in the bootprocess. But this is not the time to start the
   squid proxy server.

2. Going multiuser.

   After the rcS.d scripts have been executed, init switches to the
   default runlevel as specified in /etc/inittab, usually "2".

   Init then executes the /etc/init.d/rc script which takes care of
   starting the services in /etc/rc2.d.
[....]


-- 
Brian Servis
-- 
------------------------------------------------------------------------
Mechanical Engineering              |  Never criticize anybody until you  
Purdue University                   |  have walked a mile in their shoes,
servis@purdue.edu                   |  because by that time you will be a
http://www.ecn.purdue.edu/~servis   |  mile away and have their shoes.