about the FAQ and /etc/init.d

1998-02-17 Thread John Spence
While trying to decide on the most logical place to start my
IP-Masquerading rules, I checked the faq for wisdom.

Placing a script in /etc/init.d and then working out what numeric argument
to pass to update-rc.d seemed to be the best bet.

Answer 11.3 states that scripts in /etc/init.d all take an argument which
can be either 'start', 'stop', or 'reload'Implementing my IP-Masq
rules don't really require a start, stop or reload argument so would I be
better off starting them in some other way/location ?

Would the IP-Masq rules be best started from /etc/ppp/ip-up ?

-- 
John Spence [EMAIL PROTECTED]  http://www.lynx.net.au/~jspence


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: about the FAQ and /etc/init.d

1998-02-17 Thread Michael Beattie
On Tue, 17 Feb 1998, John Spence wrote:

 While trying to decide on the most logical place to start my
 IP-Masquerading rules, I checked the faq for wisdom.
 
 Placing a script in /etc/init.d and then working out what numeric argument
 to pass to update-rc.d seemed to be the best bet.
 
 Answer 11.3 states that scripts in /etc/init.d all take an argument which
 can be either 'start', 'stop', or 'reload'Implementing my IP-Masq
 rules don't really require a start, stop or reload argument so would I be
 better off starting them in some other way/location ?
 
 Would the IP-Masq rules be best started from /etc/ppp/ip-up ?
 
I use a script in /etc/rc.boot which is run automatically on boot.
I guess ip-up would do, but I think it's better to set all that sort of
stuff up on boot up.
I think there is a default setserial one that you could look at... even
though there is not much to look at :) (am I right to say it is a 
default?)


   Michael Beattie ([EMAIL PROTECTED])

---
  Bother, said Pooh, as he heard, Will the Defendant please rise.
---
Debian GNU/Linux  Ooohh You are missing out!


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: about the FAQ and /etc/init.d

1998-02-17 Thread John Spence
  Would the IP-Masq rules be best started from /etc/ppp/ip-up ?
  
 I use a script in /etc/rc.boot which is run automatically on boot.
 I guess ip-up would do, but I think it's better to set all that sort of
 stuff up on boot up.
 I think there is a default setserial one that you could look at... even
 though there is not much to look at :) (am I right to say it is a 
 default?)

I ended up creating a script in /etc/init.d which implements the IPMasq
rules fine at startup.  I think what led to this was that most of the
references I've seen to startup scripts were about /etc/rc.local on other
distributions and the Deb FAQ equates rc.local questions with /etc/init.d

It did seem like overkill though as I hadn't even thought about placing a
script in /etc/rc.boot

One interesting point was the update-rc.d command line I used which was

update-rc.d jmasq defaults 19

Using defaults was supposed to add symlinks for runlevels 2 to 5 but the
output of the command was the following which seems to indicate that it
did more than that. I assume that each of the following directories is
for a specific runlevel:

 Adding system startup links pointing to /etc/init.d/jmasq ...
   rc2.d/S19jmasq - ../init.d/jmasq
   rc3.d/S19jmasq - ../init.d/jmasq
   rc4.d/S19jmasq - ../init.d/jmasq
   rc5.d/S19jmasq - ../init.d/jmasq
   rc0.d/K19jmasq - ../init.d/jmasq
   rc1.d/K19jmasq - ../init.d/jmasq
   rc6.d/K19jmasq - ../init.d/jmasq



-- 
John Spence [EMAIL PROTECTED]  http://www.lynx.net.au/~jspence


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: about the FAQ and /etc/init.d

1998-02-17 Thread Joel Klecker
At 00:36 +1030 1998-02-18, John Spence wrote:
Using defaults was supposed to add symlinks for runlevels 2 to 5 but the
output of the command was the following which seems to indicate that it
did more than that. I assume that each of the following directories is
for a specific runlevel:

 Adding system startup links pointing to /etc/init.d/jmasq ...
   rc2.d/S19jmasq - ../init.d/jmasq
   rc3.d/S19jmasq - ../init.d/jmasq
   rc4.d/S19jmasq - ../init.d/jmasq
   rc5.d/S19jmasq - ../init.d/jmasq
   rc0.d/K19jmasq - ../init.d/jmasq
   rc1.d/K19jmasq - ../init.d/jmasq
   rc6.d/K19jmasq - ../init.d/jmasq

S* means, execute with the argument start; K* means, execute with the
argument stop; so, runlevels 2-5 will start the script, and runlevels
0, 1, and 6 will stop it.

--
Joel Espy Klecker Debian GNU/Linux Developermailto:[EMAIL PROTECTED]
http://www.espy.org/http://www.debian.org/



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: about the FAQ and /etc/init.d

1998-02-17 Thread John Spence
  Adding system startup links pointing to /etc/init.d/jmasq ...
rc2.d/S19jmasq - ../init.d/jmasq
rc3.d/S19jmasq - ../init.d/jmasq
rc4.d/S19jmasq - ../init.d/jmasq
rc5.d/S19jmasq - ../init.d/jmasq
rc0.d/K19jmasq - ../init.d/jmasq
rc1.d/K19jmasq - ../init.d/jmasq
rc6.d/K19jmasq - ../init.d/jmasq
 
 S* means, execute with the argument start; K* means, execute with the
 argument stop; so, runlevels 2-5 will start the script, and runlevels
 0, 1, and 6 will stop it.

AH! It makes sense now, thanks.

So I'd better mimick some of the other scripts and add start/stop
parameters or move it to /etc/rc.boot/

-- 
John Spence [EMAIL PROTECTED]  http://www.lynx.net.au/~jspence


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .