Power outage again...

[David A. Bandel]

On Mon, 25 Mar 2002 20:30:11 -0500
begin  Bill Day <bill at daysdomain.com> spewed forth:

> Well, twice in the last few weeks the power has gone out and of course
> when my box comes back up(yes a BackUPS is on it, but the outage always
> outlasts my BackUPS, arg) I ahve to start/restart services namely dhcpd,
> sshd, smbd, nmbd, apache and pmfirewall (just to make sure that nothing
> was wiered out during reinit of eth0).
> 
> I am wondering whats going on.  a boot of the box and all is fine, the
> bash scripts in /etc/rc.d/init.d/.. all seem to work just fine...
> 
> is there some way that I can "order" these scritps to start in a certain
> order, i.e dhcpd to start prior to eth0 initing itself..?

yes, you can order the scripts, but dhcpd binds to your IP addresses
(which you don't have until the network is up).

look for an rc3.d or rc5.d on your system (/etc/rc.d/rc#.d or /etc/rc#.d)
(if you're running Slackware, you're SOL here, you'll need to just hack up
/etc/rc.d/rc.inet2, et. al.).

the "files" in this directory are links to init.d/xxx.  Start order comes
from the S##name, so the number is the key, starting from 00 to 99 (or 000
to 999).  Just change the number and you'll change the order of daemon
startup.

> 
> its nothing major, just annoying, but I would just soon not have to do
> this all the time.
> 
> The box is a modified other than kernel eD2.4.
> 
> latest Apache, latest sshd/openssl   These are my primary concerns as
> the outside connection comes up wonderfully, but if I am away, I am
> unable to connect via sshd and restart other services etc...
> 
> Any tips pointers would be greatly appreciated

yes, find out _why_ stuff isn't starting and fix it.  Most likely you'll
find it's an environment problem (i.e., you can run all the init.d/
scripts from the command line and they work, but they don't work from
bootup).  This is because you have an environment variable (PATH) set and
init doesn't during system startup.  Alternately (and you did say eD2.4
from Caldera), you don't have certain modules you need loaded during
bootup (but they do get loaded later), so the service can't start
(example, you're not loading the 8139too module, so networking can't start
because the ethernet driver isn't loaded).

Check your logs, watch the bootup screens.  If you can't figure it out,
write down what's going on during bootup (get rid of the pretty screen and
watch what's really going on) -- most important is the message where it
stops, and what might be coming next (if you can figure that out from your
/etc/rc.d/rc3.d (or rc5.d) symlinks.


Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
		-- Nemesis Racing Team motto