Bug 212419
Summary: | --pipe doesn't work for "more" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kim Lux <lux> |
Component: | rpm | Assignee: | Paul Nasrat <nobody+pnasrat> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | ||
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: | 2007-08-09 20:17:46 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
Kim Lux
2006-10-26 18:36:29 UTC
Why bother with --pipe? Try this instead: rpm -i ... 2>&1 | more NOTABUG I know that the outputs can be redirected to more. But why doesn't --pipe work for more ? If it doesn't work as advertised, then shouldn't it be deleted from the man page ? If it doesn't work with more, isn't that a bug, even though there is a work around ? Just because there is a work around doesn't mean it isn't a bug. The --pipe option works for what it was intended for. E.g. The --pipe option works for what it was intended for. E.g. rpm -qa --last Meanwhile, "... 2>&1 | more" works for what it was intended for as well. The issue is likely more's detection of whether it is attached to a tty, not otherwise. There's certainly nothing exotic or different about rpm's --pipoe implementation. In fact, this command "works" exactly as expected: rpm -qa --pipe more In fact, this command rpm -i time-1.7-27.2.2.1.i386.rpm --pipe more "works" as well, there's just no output on stdout for more to page. So I suspect that what you are missing is that --pipe doesn't handle stderr. NOTABUG Yup... > I expected the output of rpm to be piped to more so that I could page through > the errors. It wasn't. It was frustrating at the time. --pipe does what it's intended to do, but would be nice if the errors got logged someplace (bug #203796) |