Donna, I've run into similar problems in the past when I forget that at system start time, there's usually no PATH environment variable defined, so the scripts I write tend to fail. To get more debugging information, you can put a "set -x" command right after the #!/whatever line you have in the /etc/init.d/tomcat script. That might help figure out what's really going on.
Mark Post -----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
