I am running the 2.4.7 kernel, and have the exact same problem. I think it may have
something to due with being started too soon. I was going to put a sleep command in,
just to see if it helped, but
I haven't gotten around to it yet.
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] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Donna Awald [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 15, 2002 10:58 AM
To: [EMAIL PROTECTED]
Subject: SLES7 for S/390 and Tomcat 4.03 Automating Startup
Problem
I have installed the tar version of Tomcat 4.03 and want to
incorporate it
in the /etc/init.d start up process. I took the skeleton script and
modified it for Tomcat. I can successfully start it manually with the
/etc/init.d/tomcat start command, and stop it with the
/etc/init.d/tomcat
stop command. I placed the appropriate links in rc3.d directory via
the
insserv command and the comments in the tomcat start script. When I
shutdown reboot the system, the tomcat script runs but tomcat is not
started. I placed many echoes throughout the script to verify the
commands
are being issued but the processes never start. Has anyone run across
this
before? I have tried the following scenarios in the startup script:
startproc /tomcat/bin/startup.sh
. /tomcat/bin/startup.sh
/tomcat/bin/startup.sh
/tomcat/bin/catalina.sh start
startproc /tomcat/bin/catalina.sh start
each of these worked when I issue the commands manually using
/etc/init.d/tomcat start, but not during reboot time.
I have SuSE Linux running on Intel platforms with the same version of
Tomcat
and using the equivalent one to the first one above works fine.
(start_daemon instead of startproc) So, I am really perplexed as to
why it
is not working.
Any help you could give would be greatly appreciated.
Thanks,
Donna Awald
