bugattr - Bugs: bug #33417, use reasonable exit statuses


bug #33417: use reasonable exit statuses

Submitter:  Christoph Anton Mitterer <calestyo>
Submitted:  Fri 27 May 2011 08:13:49 PM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment (Rich Markup)

Comment Type & Canned Response:
       No canned response available


Fri 27 May 2011 08:13:49 PM UTC, original submission:  


Currently it seems to me that setfattr/getfattr don't use exit statuses != 0 at all.
Could you please add this (very important) functionality?

Exit codes (!= 0) should at least be provided for the following cases:
- Trying to read/write XATTRs when not supported by the underlying filesystem.
- Trying to read/write XATTRs when not allowed (e.g. not the "user" namespace, or on files that are not regular or not directories.
- Trying to read an XATTR that doesn't exist (currently it's not easily possible to determine whether an XATTR is set or not.
- etc.


Christoph Anton Mitterer <calestyo>


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

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by calestyo (Submitted the item)

    There are 0 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.





    No changes have been made to this item

    Back to the top

    Powered by Savane 3.9