It turns out that the init script for tomcat on Suse 10.3 is flawed and will not work unless a user is actually logged in.
I finally just gave up and installed Tomcat 6.0.14 which incidentally is not available in an RPM but the installation is literally just untaring and putting it in some directory. Then it was just a matter of making a simple startup script:
Code:
#!/bin/bash
#
# tomcat boot script
RETVAL=$?
CATALINA_HOME="/tomcat6"
export JAVA_HOME="/usr/lib/jvm/java"
case $1 in
start)
sh /tomcat6/bin/startup.sh
;;
stop)
sh /tomcat6/bin/shutdown.sh
;;
restart)
sh /tomcat6/bin/shutdown.sh
sh /tomcat6/bin/startup.sh
;;
esac
exit 0
Placing it in /etc/init.d, Chmod +X starttomcat.sh
For some reason it would still return errors when set to boot so I just added a cronjob that executed "/etc/init.d/starttomcat.sh start" on boot.
This may not be the most elegant solution but until the tomcat RPM is fixed this is the only thing that worked for me. (The premade boot script also fails to work on my full desktop Suse 10.3 install so this is not an isolated occurance)
This is probably a better solution anyway since I decided not to use Apache and route to tomcat. Tomcat 5 was the first version to have a built in component for serving static content, Tomcat 6 has since improved making apache not needed (unless one wants/needs PHP)