When running "paxctl-ng -d" twice, the second invocation returns status code 1, with no error message. This is quite counter-intuitive, I suggest returning 0 when user.pax.flags has already been removed (I actually went for "paxctl-ng -d" instead of "setfattr -x user.pax.flags" because setfattr complains when the xattr is not present).
Created attachment 359516 [details, diff] Return 0 on subsequent runs of paxctl-ng -d We want to record a failure, for example, if we don't have permissions to delete the xattr filed, but it is there. However, we don't want to record a failure if the field was never there in the first place because in a sense paxctl-ng -d does leave the file without the user.pax.flags field. Please test this patch. It fixes the problem for me.
(In reply to Anthony Basile from comment #1) > Please test this patch. It fixes the problem for me. I've pushed the fix to the repository: http://git.overlays.gentoo.org/gitweb/?p=proj/elfix.git;a=summary I don't think I'll add an elfix-9999 though.
(In reply to Anthony Basile from comment #1) > Please test this patch. It fixes the problem for me. Works fine for me, thanks.
(In reply to Maxim Kammerer from comment #3) > (In reply to Anthony Basile from comment #1) > > Please test this patch. It fixes the problem for me. > > Works fine for me, thanks. This is in the tree with sys-apps/elfix-0.8.4. Queued for stabilization in 30 days.
