Opened 21 years ago
Closed 18 years ago
#709 closed defect (wontfix)
unknown_command | tar xv
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | lowest | Milestone: | |
| Component: | nALFS - Back End (XML Handlers) | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
unknown_command | tar xv
returns 0, not causing execution to stop when unpacking.
Change History (5)
comment:1 by , 20 years ago
| Version: | CVS → SVN |
|---|
comment:2 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 19 years ago
I don't believe that's true. The bug was not a complaint about handling of unknown compression formats, it's a complaint about the shell's handling of failures of the non-trailing commands in a pipe.
The issue is that if the first command in a two-command pipe does not exist, or is not executable (as opposed to being executable but returning failure), the entire pipe command is not executed, but the shell does not return a failure error level. There is a shopt you can set in bash to work around this behavior, but it's bash specific and we didn't want to build bash-specificity into nALFS.
The true solution to this problem is to not use the shell for piping commands together, but to do it directly in the application.
comment:4 by , 19 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Ah, this bug is more general that I first thought. The work involved in this is beyond the scope of our 'maintainance mode' IMO and the lack of error reports from users seems to suggest this too. I'll reopen though in order to spark discussion.
comment:5 by , 18 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | reopened → closed |
No discussion sparked and no new reports on this very old bug so closing.
Old bug that has been fixed in current versions. See unpack.c's handling of an unknown decompressor.