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@xxxxxxxxxx>
---
sys-utils/setpriv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-utils/setpriv.c b/sys-utils/setpriv.c
index 907845545..f68e6c48a 100644
--- a/sys-utils/setpriv.c
+++ b/sys-utils/setpriv.c
@@ -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);
--
2.48.1
