Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] jetty for production : run as a service + log management

Hi Joakim,

thanks for your help, I have read the rest of your message. Before
anything else I want to clear out something :

Le 14/09/2017 à 21:40, Joakim Erdfelt a écrit :
> This behavior, forking a new instance if --exec is used is common and
> desired.

I understand very well it is desired, even if I don't understand why it
is needed for options other than --exec like --module=logging-logback.
Than one makes the instance to fork too, even if --exec is not enabled.

My original point was about jetty.sh : It can't handle forking jetty
well. This is a fact, I have explained this in the mentionned github
issue :  I would suggest to use pgrep -P <mainprocesspid> so the script
can wait that the child processed died BEFORE the state file is removed.

I'll do a PR about it if get time to...


Back to the top