From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH 02/45] keyctl.2: Add LIBRARY section
Date: Sat, 11 Sep 2021 18:00:35 +0200 [thread overview]
Message-ID: <20210911160117.552617-3-alx.manpages@gmail.com> (raw)
In-Reply-To: <20210911160117.552617-1-alx.manpages@gmail.com>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
man2/keyctl.2 | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/man2/keyctl.2 b/man2/keyctl.2
index 4e3ca5dac..226ae2800 100644
--- a/man2/keyctl.2
+++ b/man2/keyctl.2
@@ -28,6 +28,13 @@
.TH KEYCTL 2 2021-08-27 Linux "Linux Key Management Calls"
.SH NAME
keyctl \- manipulate the kernel's key management facility
+.SH LIBRARY
+Standard C library
+.RI ( libc ", " -lc )
+.PP
+Alternatively, Linux Key Management Utilities
+.RI ( libkeyutils ", " -lkeyutils );
+see NOTES.
.SH SYNOPSIS
.nf
.BR "#include <linux/keyctl.h>" " /* Definition of " KEY* " constants */"
@@ -1958,8 +1965,6 @@ library.
(The accompanying package provides the
.I <keyutils.h>
header file.)
-When employing the wrapper in that library, link with
-.IR \-lkeyutils .
However, rather than using this system call directly,
you probably want to use the various library functions
mentioned in the descriptions of individual operations above.
--
2.33.0
next prev parent reply other threads:[~2021-09-11 16:01 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 16:00 [PATCH 00/45] Add LIBRARY section (based on FreeBSD manual pages) Alejandro Colomar
2021-09-11 16:00 ` [PATCH 01/45] _exit.2: Add LIBRARY section Alejandro Colomar
2021-09-11 16:00 ` Alejandro Colomar [this message]
2021-09-11 16:00 ` [PATCH 03/45] gamma.3: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 04/45] request_key.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 05/45] write.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 06/45] wait4.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 07/45] wait.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 08/45] vmsplice.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 09/45] vm86.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 10/45] vhangup.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 11/45] vfork.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 12/45] utimensat.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 13/45] utime.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 14/45] ustat.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 15/45] userfaultfd.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 16/45] unshare.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 17/45] uname.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 18/45] umount.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 19/45] tkill.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 21/45] unlink.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 22/45] umask.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 23/45] truncate.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 24/45] timer_getoverrun.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 25/45] timerfd_create.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 26/45] timer_delete.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 27/45] timer_create.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 28/45] time.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 29/45] tee.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 30/45] syslog.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 31/45] sysinfo.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 32/45] syscall.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 33/45] sync_file_range.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 34/45] sync.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 35/45] symlink.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 36/45] swapon.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 37/45] subpage_prot.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 38/45] statx.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 39/45] stat.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 40/45] spu_run.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 41/45] spu_create.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 42/45] splice.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 43/45] socketpair.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 44/45] socketcall.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 45/45] sigwaitinfo.2: " Alejandro Colomar
2021-09-11 18:29 ` [PATCH 00/45] Add LIBRARY section (based on FreeBSD manual pages) Eugene Syromyatnikov
2021-09-11 18:40 ` Alejandro Colomar (man-pages)
2021-09-11 22:24 ` Eugene Syromyatnikov
2021-09-11 22:37 ` Alejandro Colomar (man-pages)
2021-09-13 18:42 ` Stefan Puiu
2021-09-14 8:30 ` Eugene Syromyatnikov
2021-09-14 8:32 ` Eugene Syromyatnikov
2021-09-15 20:20 ` Alejandro Colomar (man-pages)
2021-09-17 8:12 ` Stefan Puiu
2021-09-17 8:21 ` Florian Weimer
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=20210911160117.552617-3-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).