Daemonizing Jetty?

[Wessel, Keith]

Hi, all,

I know this is a purely Jetty question, foregive me if it's off-topic. I figured others might have run into this, too.

I've been using jetty.sh (included with the Jetty package) to start/stop Jetty. Seems it's using a simple '&' backgrounding method to daemonize jetty.sh. This is fine as long as I'm starting/stopping Jetty from the local system. It's when I do:

ssh other-IDP-note jetty.sh start

that I run into problems. The non-interactive nature of things seems to gum up the works. My ssh command never returns me to a prompt on the local system. I assume it's waiting for the backgrounded process to start and, in fact, verified this with a simple one-line bash script: sleep 15 &. It terminates immediately when run locally but hangs for 15 seconds when passed to ssh asa  command to run remotely.

I know I can get around this with the -t option to ssh to tell ssh to force a pseudo terminal. But is there any Jetty command-line arg that tells Jetty to daemonize? I imagine, if there was, it would probably be used in jetty.sh in place of &. But I figured it couldn't hurt to ask. My Google searches so far reveal no such option.

I'm far happier with Jetty's ease of configuration and speed so far than I was with Tomcat, but Tomcat at least knew how to fork its own Daemon process.

Thanks,
Keith