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

 
 

bug #33417: use reasonable exit statuses

Submitted by:  Christoph Anton Mitterer <calestyo>
Submitted on:  Fri 27 May 2011 08:13:49 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: NoneStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

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

Hi.

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.

Cheers,
Chris.

Christoph Anton Mitterer <calestyo>

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup