Bug 177242
Summary: | Bash is not ignoring SIGPIPE | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brian Gerst <brgerst> |
Component: | bash | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-01-10 14:27:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian Gerst
2006-01-08 05:05:35 UTC
Please provide a smaller, self-contained test case. I haven't been able to reproduce this. while :; do echo foo; done | head -n1 ..generates a SIGPIPE, and does not give out a warning. What does that line do when you run it? I found the culprit. cg-log does "trap exit SIGPIPE". Commenting out this line silences the error. Since older bashes didn't give the error message with this trap in place, is it a bash regression, or should the script just not use the trap? Reported upstream. Thanks for the smaller test case: bash -c 'trap exit SIGPIPE; echo foo' | : Intentional behaviour change. |