[jetty-dev] [jira] (JETTY-1234) [jetty.sh] Redhat doesn't have start-stop-daemon available

Adrien Kunysz
commented on JETTY-1234

[jetty.sh] Redhat doesn't have start-stop-daemon available

The alternate path does not work properly as it keeps stdout and stderr open. Which means that if you were to start jetty from ssh, ssh will never exit. For example:

$ ssh $host sudo /etc/init.d/jetty6 start

Found JAVA=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java in JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64

Starting Jetty: STARTED Jetty Tue Jun 26 14:59:41 BST 2012

[hang forever]

This works around the problem:

— /etc/init.d/jetty6 2012-06-26 14:59:37.000000000 +0100

+++ /etc/init.d/jetty6.ok 2012-06-26 14:59:29.000000000 +0100

@@ -532,12 +532,12 @@

touch $JETTY_PID

chown $JETTY_USER $JETTY_PID

su - $JETTY_USER -c "

- $RUN_CMD &

+ $RUN_CMD &> /dev/null &

PID=\$!

disown \$PID

echo \$PID > $JETTY_PID"

else

- $RUN_CMD &

+ $RUN_CMD &> /dev/null &

PID=$!

disown $PID

echo $PID > $JETTY_PID

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators .

For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email