Jetty
  1. Jetty
  2. JETTY-1234

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

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 7.1.0
    • Fix Version/s: 7.1.0
    • Component/s: Packaging
    • Labels:
      None
    • Number of attachments :
      0

      Description

      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 .

        Activity

        Hide
        Adrien Kunysz added a comment -

        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
        Show
        Adrien Kunysz added a comment - 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
        Hide
        Jan Bartel added a comment -

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

        Show
        Jan Bartel added a comment - This issue has been moved to jetty eclipse bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=396573
        Jan Bartel made changes -
        Field Original Value New Value
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Duplicate [ 3 ]

          People

          • Assignee:
            Joakim Erdfelt
            Reporter:
            Joakim Erdfelt
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: