Actually, you don't need it. There's a fix for /etc/init.d/rc that corrects this. I posted an explanation of the problem a week or so ago.
The problem is that the blogd daemon that logs boot-time messages is killed before the last daemon finishes using it. The kill propagates back to the daemon as a SIGHUP, which kills it too. I'll repost my original comment with the patch. > -----Original Message----- > From: Gustavson, John (IDS ECCS) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 10:52 AM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] Things not starting at IPL > > > Exactly. S99donothing will be at the end as long as you > don't have anything else is S99, after S99d (eg. S99e ~ S99z.) > > > Regards > > John Gustavson > Enterprise Central Software Services (ECSS) > 570 Washington Street - 2nd floor > New York, New York, 10080-6802 > > Telephone: 1-212-647-3793 > Fax: 1-212-647-3321 > Email: [EMAIL PROTECTED] > > > > -----Original Message----- > From: James Melin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 10:45 AM > To: [EMAIL PROTECTED] > Subject: Re: Things not starting at IPL > > So by 'this runs at the end of all our start up scripts' you > mean anything > in rc.x that starts with 'S' or somethign else? > > > > |---------+----------------------------> > | | "Gustavson, John | > | | (IDS ECCS)" | > | | <[EMAIL PROTECTED]| > | | nge.ml.com> | > | | Sent by: Linux on| > | | 390 Port | > | | <[EMAIL PROTECTED]| > | | IST.EDU> | > | | | > | | | > | | 04/01/2003 09:36 | > | | AM | > | | Please respond to| > | | Linux on 390 Port| > | | | > |---------+----------------------------> > > >------------------------------------------------------------- > -----------------------------------------------------------------| > | > | > | To: [EMAIL PROTECTED] > | > | cc: > | > | Subject: Re: Things not starting at IPL > | > > >------------------------------------------------------------- > -----------------------------------------------------------------| > > > > > We created a script S99donothing in /etc/init.d/rc3.d as follows: > > case "$1" in > start) > echo -n "Doing nothing" > sleep 3 > rc_status -v > ;; > > This runs at the end of all our start up scripts. > > > Regards > > John Gustavson > Enterprise Central Software Services (ECSS) > 570 Washington Street - 2nd floor > New York, New York, 10080-6802 > > Telephone: 1-212-647-3793 > Fax: 1-212-647-3321 > Email: [EMAIL PROTECTED] > > > > -----Original Message----- > From: James Melin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 10:30 AM > To: [EMAIL PROTECTED] > Subject: Re: Things not starting at IPL > > Could you give some details as to which startup scripts and > what specific > commands you did to allow this transition ? > > > > |---------+----------------------------> > | | "Gustavson, John | > | | (IDS ECCS)" | > | | <[EMAIL PROTECTED]| > | | nge.ml.com> | > | | Sent by: Linux on| > | | 390 Port | > | | <[EMAIL PROTECTED]| > | | IST.EDU> | > | | | > | | | > | | 04/01/2003 09:17 | > | | AM | > | | Please respond to| > | | Linux on 390 Port| > | | | > |---------+----------------------------> > > > -------------------------------------------------------------- > ----------------------------------------------------------------| > > | > | > | To: [EMAIL PROTECTED] > | > | cc: > | > | Subject: Re: Things not starting at IPL > | > > > -------------------------------------------------------------- > ----------------------------------------------------------------| > > > > > > We had the same problem with various things not starting > intermittently. > The processes are getting hup'ed if the boot process hasn't ended and > closed the log. Because these processes are writing to > the boot log, they get hup'ed too. We put in a dummy script > to sleep at > the end of the start-up scripts to allow boot to close the log and > terminate. This solved the intermittent problem. Actually > it was Ken Hall who discovered this. > > > Regards > > John Gustavson > Enterprise Central Software Services (ECSS) > 570 Washington Street - 2nd floor > New York, New York, 10080-6802 > > Telephone: 1-212-647-3793 > Fax: 1-212-647-3321 > Email: [EMAIL PROTECTED] > > > > -----Original Message----- > From: James Melin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 9:39 AM > To: [EMAIL PROTECTED] > Subject: Things not starting at IPL > > I have a situation where various things are not starting > properly at boot. > > I see the message for the httpd server on the HMC console: > Starting httpd > [ LDAP PERL PHP4 SSL ] but when I telnet in, the task is not > running and I > don't see anything in the log that truly indicates why it's > not there. > Also, JBOSS is not starting at IPL, even though the items in > etc/init.d/rc3/d are ok. (or appear to be). Lastly, one component of > DB2connect EE isn't starting either. That is the db2sysc > process, in the > 8.1 version of DB2 connect. I have had to logon as db2inst1 > and issue a > db2start command to get that to work. Nothing for it was created in > /etc/init.d or any of the rc.x sub dirs. Any insight? > > Here are the RC3.d entries for apache/jboss. I believe the links are > correct. The actual scripts themselves do function to > start/stop the tasks. > > Apache > > lrwxrwxrwx 1 root root 9 Feb 27 13:57 K02apache -> > ../apache > lrwxrwxrwx 1 root root 9 Mar 9 14:46 S23apache -> > ../apache > > Jboss: > > lrwxrwxrwx 1 root root 8 Mar 11 13:56 K01jboss -> > ../jboss > lrwxrwxrwx 1 root root 8 Mar 11 13:56 S21jboss -> > ../jboss >
