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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@codehaus.org
[jetty.sh] Redhat doesn't have start-stop-daemon available
----------------------------------------------------------

                 Key: JETTY-1234
                 URL: http://jira.codehaus.org/browse/JETTY-1234
             Project: Jetty
          Issue Type: Bug
          Components: Packaging
    Affects Versions: 7.1.0
            Reporter: Joakim Erdfelt
            Assignee: Joakim Erdfelt
             Fix For: 7.1.0


The start-stop-daemon is apparently a Debian specific feature.

Investigate if alternate paths in jetty.sh (for when 'type start-stop-daemon' is false) work on a Redhat system that specifically does not have a start-stop-daemon feature .

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
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


Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@codehaus.org
Adrien Kunysz commented on Bug JETTY-1234

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
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org
Jan Bartel closed Bug JETTY-1234 as Duplicate

This issue has been moved to jetty eclipse bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=396573

Change By: Jan Bartel (13/Dec/12 10:43 PM)
Resolution: Duplicate
Status: Open Closed
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