I'm struck by this bug because I have the tomcat user doing something else related to tomcat, so it MIGHT actually be logged in.
It strikes me as a bad idea to let a startup script create a file in /etc/init.d/. We should find a better way to clarify that it's actually a tomcat instance running rather than just any old login. catalina.sh isn't making the decision; start-stop-daemon is. I'm going to work on it. Ideas are welcome. -- tomcat fails to start with: /bin/bash already running. https://bugs.launchpad.net/bugs/632554 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in ubuntu. -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
