From 55b3fe7824c261b6b3d2a8869a8cb509fdd2569f Mon Sep 17 00:00:00 2001 From: Patrick Steinhardt Date: Thu, 20 Jul 2017 08:30:04 +0200 Subject: setpriv: document accepted formats for naming caps Since commit fbd15c4d4 (setpriv: support setting unnamed capabilities, 2017-07-17), it is possible to name capabilities not only by name, but also by their index. While using the human-readable name is usually recommended, using the index may be required in case new capabilities have been introduced to the kernel for which we have no name yet. The newly introduce format format is not documented inside of setpriv(1), though, which is being fixed in this commit. Signed-off-by: Patrick Steinhardt --- sys-utils/setpriv.1 | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'sys-utils/setpriv.1') diff --git a/sys-utils/setpriv.1 b/sys-utils/setpriv.1 index b0cc33a2b..75dadeca8 100644 --- a/sys-utils/setpriv.1 +++ b/sys-utils/setpriv.1 @@ -34,7 +34,12 @@ The argument is a comma-separated list of .BI + cap and .BI \- cap -entries, which add or remove an entry respectively. +entries, which add or remove an entry respectively. \fIcap\fR can either be a +human-readable name as seen in +.BR capabilities (7) +without the \fIcap_\fR prefix or of the format +.BI cap_N , +where \fIN\fR is the internal capability index used by Linux. .B +all and .B \-all -- cgit v1.2.3-55-g7522