Re: [jetty-users] 9.1.4 release and --daemon option

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

Current design for start.log is that it is always relative to ${jetty.base}/${JETTY_LOGS}/start.log

The origin for that decision has been lost in the sands of time.

(In other words, I can't justify that decision).

So I filed a bug for it:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=432192

--

Joakim Erdfelt <joakim@xxxxxxxxxxx>

webtide.com - intalio.com/jetty

Expert advice, services and support from from the Jetty & CometD experts

eclipse.org/jetty - cometd.org

On Mon, Apr 7, 2014 at 11:44 AM, Rob Moore <rob.moore@xxxxxxxxx> wrote:

Indeed, it is complaining about being able to write to the log directory in the start.log.

I've added the start-log-file=logs/start.log as you suggested and I find this in the logs:

java.io.IOException: Cannot write start.log to directory /opt/jetty-distribution-9.1.4.v20140401/opt/jetty-distribution-9.1.4.v20140401/logs [directory doesn't exist or is read-only]

Note the duplicate jetty home defined in the path. 

I ran jetty.sh check and see the following for JETTY_LOGS

JETTY_LOGS     =  /opt/jetty-distribution-9.1.4.v20140401/logs

What's odd is that the start.log is created in the logs directory even though jetty complains it can't write it there.

Rob