New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export for systemd ignores log flag #709
Comments
@ddollar Are you willing to merge a PR when I add some options to configure SystemD parameters? Are there any wishes how these options should be named? I think something like a --systemd prefix would be nice, like
I'm not sure how to add these parameters to the Procfile though.. Maybe something like following?
|
I've created a PR for this, by adding log and error_log options - feel free to give feedback or merge :) |
@ClikeX is this still an issue? |
Of-course, still an issue. |
@andrewmcodes In the end our team ended up not using the systemd logs as much as initially intended. So yeah, I guess this is still an issue if you really want systemd to handle your logs. It seems like @h0jeZvgoxFepBQ2C was nearly finished with #717. |
foreman/data/export/systemd/process.service.erb
Line 14 in 025de2a
Systemd template ignores the log location provided with
foreman export
. Which makes me unable to set a custom location for the process. And in turn makes the flag seem useless.Seems like an oversight to me, or is there a particular reason why it isn't included?
The text was updated successfully, but these errors were encountered: