Daemonizing Jetty?

[Wessel, Keith]

Thanks for confirming my suspicion. Looks like I'm back where I started here. Not a big deal, though.

I've checked the start.jar docs pretty thoroughly, and it looks like daemonizing isn't an option. I'm still happy with what we've got here.

Thanks fro all who weighed in.

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, July 30, 2015 3:53 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Daemonizing Jetty?

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

>
-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net