Re: Startup sequence problem
Andrew Perrin <firstname.lastname@example.org> wrote:
This is an old issue, but it's started to bug me again.
On my home machine (used to be potato 2.2.19pre17, it's now woody 2.4.18),
ipmasq and openafs-client don't start up correctly from /etc/init.d. The
scripts are there, and appear to be linked correctly, but the following
- With ipmasq, the script says "Initializing IP Masquerading..." but it
doesn't happen - packets are not forwarded. However, if I run *exactly the
same* command as the init.d script is theoretically running:
/usr/sbin/ipmasq --rules /etc/ipmasq/rules
it works fine.
- With openAFS, if I start from the init.d script it hangs the computer -
no error message, but no boot either. (I have to boot into single-user
mode and delete the links in /etc/rc*d to break out.) But if I remove the
links (so it doesn't start automatically) and then do, as root,
again, it works fine.
Does anyone have a suggestion? It's not a big deal (I only reboot about
once a month, so running:
when I do so isn't such a problem) but it's irritating.
Sounds like you are running the IPMASQ stuff before your network is
activated, i.e. you don't have any interfaces defined yet. You are
correct in that this is a sequencing problem. By doing it "manually"
you are bringing up the network first and then starting IPMASQ.
I am not familiar with all the programs you are using...especially
openAFS, so it is hard to recommend a course of action. I suggest you
examine your /etc/rcS.d/ and /etc/rc2.d/ directories find out where
your openafs-client is being called and make sure it is AFTER any other
required things (like /etc/rcS.d/S40networking, and/or
/etc/rc2.d/S10ipchains on my machine).
I am running Woody with the 2.4.18 kernel here, and things are a little
bit different (ipchains is now works like a module...etc). I start my
IPMasq and Firewall stuff in /etc/rc2.d/ now.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org