Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] 9.1.4 release and --daemon option

Thanks, Joakim. It seems that the issue is that jetty can't write to the logs directory. The directory itself is a symbolic link to another directory and this has worked in the past. I see I can set JETTY_LOGS in the configuration so that's probably a better approach at any rate. I am curious though why the symlink stopped working with 9.1.4.

On Mon, Apr 7, 2014 at 11:54 AM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
The old --daemon command line piped stdout and stderr to a file before jetty's logging kicked in.
That's all it did, no special daemonization of the process or anything.

If you still require such, define the start-log-file=<path> property instead.
   $ java -jar path/to/jetty-distribution/start.jar start-log-file=logs/start.log
This is identical functionality.

Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Mon, Apr 7, 2014 at 9:45 AM, Rob Moore <rob.moore@xxxxxxxxx> wrote:
I noticed the 9.1.4 release is out and I attempted to use it but am running into problems at startup. I noticed that the --daemon option is no longer present in the script. I'm assuming this was by design but wanted to confirm. The configuration I'm using works flawlessly for 9.1.3 so I'm not sure what's caused it to stop working in 9.1.4. Unfortunately, there's no log file created on startup so I don't have much to go on at this point.



jetty-users mailing list

jetty-users mailing list

Back to the top