diff options
| author | Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> | 2020-07-20 11:13:18 +0200 |
|---|---|---|
| committer | Andrew G. Morgan <morgan@kernel.org> | 2020-07-20 07:55:07 -0700 |
| commit | 052f08447d4244240e0da9b24cf234683d8a7647 (patch) | |
| tree | f813bff120836aac429b8202e8365b83b1b2474d | |
| parent | ce910359dc98960b27c9ceda32268bd9594fe428 (diff) | |
| download | libcap2-052f08447d4244240e0da9b24cf234683d8a7647.tar.gz | |
Manual pages; cap_get_file.3: Fix some clumsily worded text
Make the text a bit easier to read, and also fix the terms used.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
Signed-off-by: Andrew G. Morgan <morgan@kernel.org>
| -rw-r--r-- | doc/cap_get_file.3 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/cap_get_file.3 b/doc/cap_get_file.3 index c028148..ceacbaf 100644 --- a/doc/cap_get_file.3 +++ b/doc/cap_get_file.3 @@ -57,12 +57,12 @@ A NULL value for .IR cap_p is used to indicate that capabilities for the file should be deleted. For these functions to succeed, the calling process must have the -effective capability, -.BR CAP_SETFCAP , -enabled and either the effective user ID of the process must match the +.BR CAP_SETFCAP +capability in its effective set +and either the effective user ID of the process must match the file owner or the calling process must have the .B CAP_FOWNER -flag in its effective capability set. The effects of writing the +capability in its effective capability set. The effects of writing the capability state to any file type other than a regular file are undefined. .PP |