From: Nikanth Karthikesan <knikanth-l3A5Bk7waGM@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org
Subject: [PATCH] ioprio_set.2: CAP_SYS_ADMIN is not reqd to set IOPRIO_CLASS_IDLE anymore
Date: Tue, 8 Jul 2008 12:07:39 +0530 [thread overview]
Message-ID: <200807081207.39693.knikanth@suse.de> (raw)
Since linux-2.6.25 CAP_SYS_ADMIN capability is not required to set
IOPRIO_CLASS_IDLE.
Signed-off-by: Nikanth Karthikesan <knikanth-l3A5Bk7waGM@public.gmane.org>
---
man2/ioprio_set.2 | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
Index: b/man2/ioprio_set.2
===================================================================
--- a/man2/ioprio_set.2
+++ b/man2/ioprio_set.2
@@ -293,11 +293,12 @@ capability can change the priority of an
.B "What is the desired priority"
Attempts to set very high priorities
.RB ( IOPRIO_CLASS_RT )
-or very low ones
-.RB ( IOPRIO_CLASS_IDLE )
require the
.B CAP_SYS_ADMIN
-capability.
+capability. Kernel versions till 2.6.24 require
+.B CAP_SYS_ADMIN
+capability even to set very low priority
+.RB ( IOPRIO_CLASS_IDLE ).
.PP
A call to
.BR ioprio_set ()
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-07-08 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 6:37 Nikanth Karthikesan [this message]
[not found] ` <200807081207.39693.knikanth-l3A5Bk7waGM@public.gmane.org>
2008-07-08 7:17 ` [PATCH] ioprio_set.2: CAP_SYS_ADMIN is not reqd to set IOPRIO_CLASS_IDLE anymore Michael Kerrisk
[not found] ` <cfd18e0f0807080017y56441677wdf8163c520e8103f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-08 8:55 ` Nikanth Karthikesan
2008-07-08 10:11 ` Michael Kerrisk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200807081207.39693.knikanth@suse.de \
--to=knikanth-l3a5bk7wagm@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.