Flags/options should be able to be passed

[Bapabooiee]

Graylog 2 currently ignores all arguments passed to it. This means users cant:

• Specify its PID file location (for example, in Gentoo, /var/tmp/run is the standard, not /tmp.)
• Specify which configuration file to use.
• Specify where, or if, to save log files.

Unless this can be amended, this'll also probably result in less adoption of Graylog2, since distro repository devs will have to hack at its code in order to configure it meet their distribution's standards.

[lennartkoopmann]

thx, moved this up in priority

[wr0ngway]

Also running into this - my tmp dir gets cleared out pretty regularly, so doesn't make a good location for storing the tmp file. Would be nice if the ctl script managed the pid file or its location was configured in the graylog2.conf.

[Bapabooiee]

I think the PID location would be best-specified as an argument, rather than in graylog2.conf, as init scripts will need to be able to easily know/set the PIDfile location.

That said, I think /var/run/graylog2.pid would be a good, standard location for the PIDfile (if one isn't specified as a flag).

[lennartkoopmann]

Yepp.

I'll include this in the next release. Maybe one of you finds the time to integrate it?! It's pretty isolated of the other code so it should not take so long.

[pstehlik]

how about using log4j for logging?
i would be willing to pick that up in a first implementation.

workaround for log files would be directing the output to a log file of your choice like
sudo java -jar graylog2-server.jar > /var/log/graylog2.log 2>&1 &

[lennartkoopmann]

yes philip :) please wait until I merge some stuff to master in the next days. I'll let you know once it's done

[lennartkoopmann]

philip, i merged the big load of changes to master just now. you could start changing to log4j now

[lennartkoopmann]

Moved to http://jira.graylog2.org/browse/SERVER-44 as this issue tracker is being shut down! Thank you!