I had a similar problem, and changed catalina.sh to do this at the start: source /etc/profile
This was where I was setting CATALINA_HOME, and JAVA_HOME. When the script got run at startup, those vars were not yet set... Larry >>> [EMAIL PROTECTED] 01/22/03 10:20 AM >>> Has anybody had a problem with tomcat (4.0.4) starting after a reboot? Or problems starting it from the root crontab? I have no problems at all starting tomcat manually. Everything works fine that way. To automate the startup after a reboot, I am using init.d with the startup script in rc3.d. However, nothing is happening. I'm not even receiving any errors in the logs. But I can immediately start it manually with out a problem. Also I can't stop and start tomcat from a crontab. I set up a stop and start script and placed them in the root crontab, but the time comes to stop tomcat and nothing happens then the startup script should be initiated a minute later but it is a mute point since tomcat didn't stop, but nothing shows up in the logs either way. Is there a parameter or something that I am missing for this to work? I am running Tomcat 4.0.4 (as a standalone server using port 8880) on Solaris 2.7. Apache 1.3.9 is running on the server as well using port 80. Thanks in advance for the help. - Carey - -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
