On Friday, Sep 24, 2004, at 14:10 Europe/London, Martijn Koster wrote:
On Fri, 2004-09-24 at 13:25, Richard Lewis wrote:
I've just found one more problem though: it won't stop!!
# /etc/init.d/tomcat stop doesn't return any errors but I had a look and found that the directory /var/run/tomcat was empty; it seems its left no process id file. Is this why it can't stop?
I don't know how they are implemented; I don't run Debian.
But I'm unclear on your approach. you wrote tomcat.sh which translates init.d-style start/stop arguments to calls into tomcat's start/stop scripts (which internally call catalina.sh with start/stop arguments). Then you're writing another init.d-style script which calls the first. Why write 2 separate scripts?
OK, sorry, I just didn't realise it existed. :-( I'm using it now.
But it still doesn't stop properly and I think (from switching off --quiet) that its because start-stop-daemon is looking for a process called catalina.sh (I still can't get it to create a process id file) which it doesn't find because the process is called 'java'.
So I've resorted to a less elegant solution:
stop) $DAEMON stop
Thanks for your help.
Richard