Daemonizing Jetty?

[Cantor, Scott]

On 7/30/15, 4:30 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:



>Is it backgrounding for Scott and others? If so, something's clearly off with my configuration.

I'm mis-remembering, I background the command to daemonize it.

For the record, what I do is basically this:

# Prepare the command to run by adjusting the output of the --dry-run
JETTY_CMD="$JAVA_HOME/bin/java -jar $JETTY_HOME/start.jar --dry-run jetty.home=$JETTY_HOME jetty.base=$JETTY_BASE"
JETTY_START=$($JETTY_CMD | sed -e 's/\\$//' | tr -d '\n')


Then I start it with:

cd $JETTY_BASE
    $JETTY_START >$JETTY_BASE/logs/stdout.log 2>$JETTY_BASE/logs/stderr.log &


The setuid is then handled by Jetty. I didn't recall that the jetty.sh script's support for a user ID actually allows privileged port use. It didn't back when I originally tried it.

-- Scott

>