[ale] RedHat chkconfig & init scripts

[Jeff Lightner]

Yes to execute bit.  It is obviously OK since it works on the startup.  

Yes to the K01 stuff being executable (did ls -lL to follow the symbolic
links before I tried the reboots).

No env variables (or unPATHed utilities) like that - I'm an experienced
cron/init script writer.  Cron has same requirement about PATHs etc...
I've done this successfully on HP-UX and Solaris just not had to do it
on RHEL before.   I'm thinking there's some other less obvious thing
going on.

The stop section is just like the start section except it uses the
keyword "stop".

Again the issue isn't that it complains about the script.   The issue is
it simply doesn't ATTEMPT to run it on shutdown.   

-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of Jim
To: ale at ale.org
Popovitch
Sent: Thursday, March 29, 2007 4:02 PM
To: Atlanta Linux Enthusiasts
Subject: Re: [ale] RedHat chkconfig & init scripts

On Thu, 2007-03-29 at 15:55 -0400, Jeff Lightner wrote:
> Yep.  I have it as K01pc1_mid_tier.   - the next thing to be stopped
is
> K03dataeng and it runs fine.
> 
> On start it is the last thing started (S99pc1_mid_tier).

Couple of other things to check...

Is the execute bit set on /etc/init.d/pc1_mid_tier ?

Can you execute /etc/rc3.d/S99pc1_mid_tier
and /etc/rc3.d/K019pc1_mid_tier?  (to make sure the symlinks are
correct)

Does /etc/init.d/pc1_mid_tier depend on any env variables that might not
exist at shutdown?  Things like $PATH, $LANG, etc.

-Jim P.

_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale