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

is IgnoreSIGPIPE=false needed ? #38

Closed
a-detiste opened this issue Nov 20, 2014 · 3 comments
Closed

is IgnoreSIGPIPE=false needed ? #38

a-detiste opened this issue Nov 20, 2014 · 3 comments
Labels

Comments

@a-detiste
Copy link
Contributor

I guess it would be safer to set IgnoreSIGPIPE=false in every service. (static & generated)

http://lists.freedesktop.org/archives/systemd-devel/2014-July/021567.html

https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=19;filename=cron-3.0pl1-124.2-nmu.diff;att=1;bug=756047

@a-detiste a-detiste changed the title is IgnoreSIGPIPE=false needed ? is IgnoreSIGPIPE=false needed ? Nov 20, 2014
@kstep
Copy link
Member

kstep commented Nov 20, 2014

IMHO, if some movement around the default value of this parameter in systemd, we should stick it to false to avoid possible unexpected issues.

@a-detiste
Copy link
Contributor Author

after a quick survey, this is set for all .service that may start a subshell: at , cron , kdm , debug-shell ...
so I'll follow this pattern. It's in systemd since 2011 (https://gitorious.org/baserock-morphs/systemd/commit/353e12c) and all the other .service have already been fixed since; so I doubt the default will be changed.

@a-detiste
Copy link
Contributor Author

... and while true; do echo XXXX; done | head -n 10 breaks horribly and fills up the journal with echo's I/O error.

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

No branches or pull requests

2 participants