]> git.ipfire.org Git - thirdparty/util-linux.git/commitdiff
setpriv: consistently use "<caps>" to indicate a list of capabilities
authorBenno Schulenberg <bensberg@telfort.nl>
Sun, 2 Feb 2025 16:06:23 +0000 (17:06 +0100)
committerKarel Zak <kzak@redhat.com>
Mon, 3 Feb 2025 12:30:05 +0000 (13:30 +0100)
The existing "<caps,...>" did not indicate that each capability name
must be preceded by "+" or "-".  Also, to indicate that the list needs
to be separated by commas, one would have to use "<cap>[,...]", not
"<cap,...>".  So... instead of trying to cram all that info in there,
just say "<caps>", like for --bounding-set.

Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
sys-utils/setpriv.c

index 90784554539af2ff28014830ec49c6e2b46400b9..f68e6c48a7d2bf9d30665eaf51d2af6ea2da0612 100644 (file)
@@ -134,8 +134,8 @@ static void __attribute__((__noreturn__)) usage(void)
        fputs(USAGE_OPTIONS, out);
        fputs(_(" -d, --dump                  show current state (and do not exec)\n"), out);
        fputs(_(" --nnp, --no-new-privs       disallow granting new privileges\n"), out);
-       fputs(_(" --ambient-caps <caps,...>   set ambient capabilities\n"), out);
-       fputs(_(" --inh-caps <caps,...>       set inheritable capabilities\n"), out);
+       fputs(_(" --ambient-caps <caps>       set ambient capabilities\n"), out);
+       fputs(_(" --inh-caps <caps>           set inheritable capabilities\n"), out);
        fputs(_(" --bounding-set <caps>       set capability bounding set\n"), out);
        fputs(_(" --ruid <uid|user>           set real uid\n"), out);
        fputs(_(" --euid <uid|user>           set effective uid\n"), out);