Skip to content
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

Gracefully handle SIGPIPE #1531

Closed
rossmcdonald opened this issue Jul 21, 2016 · 1 comment
Closed

Gracefully handle SIGPIPE #1531

rossmcdonald opened this issue Jul 21, 2016 · 1 comment

Comments

@rossmcdonald
Copy link
Contributor

Earlier versions of journald would send a SIGPIPE to any systemd processes when journald was restarted. So far we have bypassed this issue by redirecting STDOUT and STDERR to the traditional log paths, however in case users opt to use journald it would make sense to handle SIGPIPEs in a graceful manner to ensure the service doesn't crash when journald is restarted.

A similar fix was applied to Docker here: jwhonce/docker@b7f60f7

@rossmcdonald
Copy link
Contributor Author

Moving this to a doc issue here: influxdata/docs.influxdata.com-ARCHIVE#548

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant