[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #22708] Return status 126, 127 are incorrectly interpreted by xargs
From: |
James Youngman |
Subject: |
[bug #22708] Return status 126, 127 are incorrectly interpreted by xargs |
Date: |
Mon, 24 Mar 2008 00:02:02 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080129 Iceweasel/2.0.0.12 (Debian-2.0.0.12-1) |
URL:
<http://savannah.gnu.org/bugs/?22708>
Summary: Return status 126, 127 are incorrectly interpreted
by xargs
Project: findutils
Submitted by: jay
Submitted on: Monday 03/24/2008 at 00:02
Category: None
Severity: 2 - Minor
Item Group: Wrong result
Status: None
Privacy: Public
Assigned to: jay
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.1.20
Fixed Release: None
_______________________________________________________
Details:
According to the xargs documentation, the xargs utility is supposed to return
status 126 or 127 if the command canot be run. However, xarsg returns 126 if
the utility returns 126, and 127 if the utility returns 127.
That means that when xargs returns 126, you can't be sure whether it's
because the utility could not be run, or that it could be run but it returned
126.
This problem is addressed by the code changes included in Leslie Polzer's
Summer of Code work, but this has not yet been merged.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?22708>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #22708] Return status 126, 127 are incorrectly interpreted by xargs,
James Youngman <=