Description of problem: Attached is a tiny patch that allows "tolerant" behavior, i.e. proceeding even if priority could not be set. This might be of use in case something (selinux, old kernel, etc.) does not allow the requested scheduling priority to be set. This could be to some extend done as follows: ionice -c3 command || command but the downside is that one could not really tell if what failed was setting priority or command itself, which could result in duplicate command run. This patch solves the situation, so that user can do ionice -t -c3 command instead. Version-Release number of selected component (if applicable): Applies to util-linux-ng-2.13.1-9
Created attachment 303524 [details] Patch to allow ionice to proceed even in case it could not set priority
Redirected to the upstream mailing list. Thanks.