bugfindutils - Bugs: bug #20891, exit status enhancement for xargs


bug #20891: exit status enhancement for xargs

Submitter:  None
Submitted:  Sat 25 Aug 2007 02:01:34 AM UTC
Votes: 80
Category:  xargs Severity:  1 - Wish
Item Group:  None Status:  Wont Fix
Privacy:  Public Assigned to:  jay
Originator Name:  Philip Rowlands Originator Email:  -email is unavailable-
Open/Closed:  Closed Release:  None
Fixed Release:  None
* Mandatory Fields

Add a New Comment Rich Markup

Sun 19 May 2024 12:20:15 PM UTC, comment #5: 

This is not answer-is-no-forever.  If you can come up with a usable scheme which doesn't cause compatibility issues we can discuss this further.

James Youngman <jay>
Group administrator
Sun 19 May 2024 12:18:43 PM UTC, comment #4: 

If the current behaviour complies with POSIX, I don't think there is a bug to fix here.

Probably, any convenience gained by changing this is obviated by the incompatibility caused by the change.

James Youngman <jay>
Group administrator
Tue 05 Nov 2013 09:21:33 AM UTC, comment #3: 

Why this is waiting from 2007y ? it is 6 years!
This is strongly recommended improove exit codes. Unfortunately we chould save old beavior. What is my opinion:

1. add another option for switch on new exit code table
2. for exitcodes 0 to 123, xargs should check the biggest one from execution and return this
3. code 255 should be routed as is without mapping to 144. this is unneeded. who use them?
4. exitcode 1, unusable at now. map this to 124.

and should be add another option, when command returns any 'disaster' exits, script programmer could decide break or continue xargs execution.

Grzegorz Szyszlo <znik>
Sun 26 Jul 2009 11:30:02 PM UTC, comment #2: 

If you had indicated who you were, O Anonymous, I could have helped you better I think.  But anyway, I can't reproducte the problem I think you're describing with findutils 4.4.0 or 4.5.6-git.

~$ echo a b c | xargs false ; echo $?

James Youngman <jay>
Group administrator
Thu 23 Jul 2009 05:27:17 PM UTC, comment #1: 

It seems incompatible with other platforms' xargs implementation as well as even the find, that if the command formed by xarg encounters an error, no error status is returned. I will file a bug.

Sat 25 Aug 2007 02:01:34 AM UTC, original submission:  

Please consider providing an option to govern the exit status passed by xargs from the subprocessses which it launches.

Alternative modes to the current behaviour might include returning the maximum exit status, the minimum, or the bitwise OR.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


   bug dependencies.

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by znik (Voted in favor of this item)
  • -email is unavailable- added by znik (Posted a comment)
  • -email is unavailable- added by jay (Posted a comment)

    There are 80 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-05-19 jay StatusNone Wont Fix
        Assigned toNone jay
        Open/ClosedOpen Closed
    2013-11-05 znik Carbon-Copy- Added znik
    2013-09-29 jay Severity3 - Normal 1 - Wish
    2008-03-24 jay Dependencies- Depends on bugs #22708

    Back to the top

    Powered by Savane 3.13-f762.
    Corresponding source code