so there is no real reason not to allow it for non root users? removing the check is easy (3 lines) .... or are there any other issues/problems? (resend sorry for the top post stupid gmail ;) ) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: allow non root users to set io priority "idle" ?
- From: Jens Axboe <[email protected]>
- Re: allow non root users to set io priority "idle" ?
- From: Andi Kleen <[email protected]>
- Re: allow non root users to set io priority "idle" ?
- References:
- allow non root users to set io priority "idle" ?
- From: dragoran <[email protected]>
- Re: allow non root users to set io priority "idle" ?
- From: Andi Kleen <[email protected]>
- Re: allow non root users to set io priority "idle" ?
- From: dragoran <[email protected]>
- Re: allow non root users to set io priority "idle" ?
- From: Andi Kleen <[email protected]>
- Re: allow non root users to set io priority "idle" ?
- From: Jens Axboe <[email protected]>
- Re: allow non root users to set io priority "idle" ?
- From: dragoran <[email protected]>
- allow non root users to set io priority "idle" ?
- Prev by Date: file capabilities: clear fcaps on inode change (v3)
- Next by Date: Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
- Previous by thread: Re: allow non root users to set io priority "idle" ?
- Next by thread: Re: allow non root users to set io priority "idle" ?
- Index(es):
 |