On Wed, Sep 30, 1998 at 08:43:25AM +0200, Miquel van Smoorenburg wrote: > In article <[EMAIL PROTECTED]>, > Christopher Barry <[EMAIL PROTECTED]> wrote: > >In /etc/init.d/ I made a file called wmnetstartup.sh that contains: > > > >#!/bin/sh > >ipfwadm -A in -i -S 0.0.0.0/0 > >ipfwadm -A out -i -D 0.0.0.0/0 > > > >and then in /etc/rcS.d/ I made a symlink to that script called: > >S60wmnetstartup > > That's perfectly allright. That is indeed the way to add something > that needs to be run on boot only (no daemons, just one-time initialization). > The only nitpick I have is that you could/should have used: > > update-rc.d wmnetstartup start 60 S . > > That makes the link automatically for you. But esp. in the case of rcS.d, > where there is only one link anyway it doesn't really matter.
Just a note... I know this isn't any sort of policy or documented AFAIK anywhere but... when I make my own init.d scripts (which I don't intend to be part of a debian package ;) ) I name them "local.*" (like my ip maquerading scipt is local.ip_masq) The idea is I can be pretty sure that there wont ever be a debian package named "local.whatever" esp since this is the same convention used un "menu" to tell it a dependancy is met localy. just a thought...also...is there any reason not to run ipmasq script as S20 (default)? mine always worked that way -Steve -- /* -- Stephen Carpenter <[EMAIL PROTECTED]> --- <[EMAIL PROTECTED]>------------ */ E-mail "Bumper Stickers": "A FREE America or a Drug-Free America: You can't have both!" "honk if you Love Linux"
