diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-07-06 14:28:51 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-07-06 14:28:51 +0200 |
| commit | 28a4c58cc211900943f48d65fd42b313ce54e5a6 (patch) | |
| tree | 153dcbcc3fb2a17ae9437a157399838e350436fb /man2 | |
| parent | 168aac07bd0a48f6d99ca75354e8ef77ae26db93 (diff) | |
| download | man-pages-28a4c58cc211900943f48d65fd42b313ce54e5a6.tar.gz | |
intro.1, localedef.1, memusage.1, memusagestat.1, bpf.2, execve.2, fork.2, keyctl.2, request_key.2, sigaction.2, signal.2, socket.2, dlopen.3, getauxval.3, gnu_get_libc_version.3, pthread_atfork.3, sem_post.3, setjmp.3, strftime.3, veth.4, locale.5, nscd.conf.5, resolv.conf.5, address_families.7, armscii-8.7, ascii.7, capabilities.7, cgroups.7, charsets.7, cp1251.7, cp1252.7, iso_8859-1.7, iso_8859-10.7, iso_8859-11.7, iso_8859-13.7, iso_8859-14.7, iso_8859-15.7, iso_8859-16.7, iso_8859-2.7, iso_8859-3.7, iso_8859-4.7, iso_8859-5.7, iso_8859-6.7, iso_8859-7.7, iso_8859-8.7, iso_8859-9.7, keyrings.7, koi8-r.7, koi8-u.7, libc.7, locale.7, man.7, network_namespaces.7, persistent-keyring.7, session-keyring.7, signal.7, unicode.7, uri.7, user-keyring.7, user-session-keyring.7: ffix: replace - with real\-
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man2')
| -rw-r--r-- | man2/bpf.2 | 6 | ||||
| -rw-r--r-- | man2/execve.2 | 6 | ||||
| -rw-r--r-- | man2/fork.2 | 2 | ||||
| -rw-r--r-- | man2/keyctl.2 | 32 | ||||
| -rw-r--r-- | man2/request_key.2 | 38 | ||||
| -rw-r--r-- | man2/sigaction.2 | 2 | ||||
| -rw-r--r-- | man2/signal.2 | 2 | ||||
| -rw-r--r-- | man2/socket.2 | 2 |
8 files changed, 45 insertions, 45 deletions
diff --git a/man2/bpf.2 b/man2/bpf.2 index e386eabbd5..a3d59e6ac9 100644 --- a/man2/bpf.2 +++ b/man2/bpf.2 @@ -84,7 +84,7 @@ below for further details. Generally, eBPF programs are loaded by the user process and automatically unloaded when the process exits. In some cases, for example, -.BR tc-bpf (8), +.BR tc\-bpf (8), the program will continue to stay alive inside the kernel even after the process that loaded the program exits. In that case, @@ -1272,10 +1272,10 @@ riscv (since Linux 5.1). .PD .SH SEE ALSO .BR seccomp (2), -.BR bpf-helpers (7), +.BR bpf\-helpers (7), .BR socket (7), .BR tc (8), -.BR tc-bpf (8) +.BR tc\-bpf (8) .PP Both classic and extended BPF are explained in the kernel source file .IR Documentation/networking/filter.txt . diff --git a/man2/execve.2 b/man2/execve.2 index 62becbdd28..7a8a134146 100644 --- a/man2/execve.2 +++ b/man2/execve.2 @@ -158,7 +158,7 @@ shared objects. This interpreter is typically .I /lib/ld-linux.so.2 for binaries linked with glibc (see -.BR ld-linux.so (8)). +.BR ld\-linux.so (8)). .\" .SS Effect on process attributes All process attributes are preserved during an @@ -857,7 +857,7 @@ program: .in +4n .EX .RB "$" " cat > script" -.B #!./myecho script-arg +.B #!./myecho script\-arg .B ^D .RB "$" " chmod +x script" .EE @@ -869,7 +869,7 @@ We can then use our program to exec the script: .EX .RB "$" " ./execve ./script" argv[0]: ./myecho -argv[1]: script-arg +argv[1]: script\-arg argv[2]: ./script argv[3]: hello argv[4]: world diff --git a/man2/fork.2 b/man2/fork.2 index a48ecabffb..7632d2dbe5 100644 --- a/man2/fork.2 +++ b/man2/fork.2 @@ -177,7 +177,7 @@ After a .BR fork () in a multithreaded program, the child can safely call only async-signal-safe functions (see -.BR signal-safety (7)) +.BR signal\-safety (7)) until such time as it calls .BR execve (2). .IP * diff --git a/man2/keyctl.2 b/man2/keyctl.2 index 6d0386c0e0..b758f331bd 100644 --- a/man2/keyctl.2 +++ b/man2/keyctl.2 @@ -82,27 +82,27 @@ The following values may be specified in .B KEY_SPEC_THREAD_KEYRING This specifies the calling thread's thread-specific keyring. See -.BR thread-keyring (7). +.BR thread\-keyring (7). .TP .B KEY_SPEC_PROCESS_KEYRING This specifies the caller's process-specific keyring. See -.BR process-keyring (7). +.BR process\-keyring (7). .TP .B KEY_SPEC_SESSION_KEYRING This specifies the caller's session-specific keyring. See -.BR session-keyring (7). +.BR session\-keyring (7). .TP .B KEY_SPEC_USER_KEYRING This specifies the caller's UID-specific keyring. See -.BR user-keyring (7). +.BR user\-keyring (7). .TP .B KEY_SPEC_USER_SESSION_KEYRING This specifies the caller's UID-session keyring. See -.BR user-session-keyring (7). +.BR user\-session\-keyring (7). .TP .BR KEY_SPEC_REQKEY_AUTH_KEY " (since Linux 2.6.16)" .\" commit b5f545c880a2a47947ba2118b2509644ab7a2969 @@ -110,7 +110,7 @@ This specifies the authorization key created by .BR request_key (2) and passed to the process it spawns to generate a key. This key is available only in a -.BR request-key (8)-style +.BR request\-key (8)-style program that was passed an authorization key by the kernel and ceases to be available once the requested key has been instantiated; see .BR request_key (2). @@ -121,7 +121,7 @@ This specifies the key ID for the .BR request_key (2) destination keyring. This keyring is available only in a -.BR request-key (8)-style +.BR request\-key (8)-style program that was passed an authorization key by the kernel and ceases to be available once the requested key has been instantiated; see .BR request_key (2). @@ -875,7 +875,7 @@ The caller must have the appropriate authorization key, and once the uninstantiated key has been instantiated, the authorization key is revoked. In other words, this operation is available only from a -.BR request-key (8)-style +.BR request\-key (8)-style program. See .BR request_key (2) @@ -1070,7 +1070,7 @@ associated with the specified key. (In other words, the .BR KEYCTL_ASSUME_AUTHORITY operation is available only from a -.BR request-key (8)-style +.BR request\-key (8)-style program; see .BR request_key (2) for an explanation of how this operation is used.) @@ -1093,7 +1093,7 @@ and the value 0 is returned. The .BR KEYCTL_ASSUME_AUTHORITY mechanism allows a program such as -.BR request-key (8) +.BR request\-key (8) to assume the necessary authority to instantiate a new uninstantiated key that was created as a consequence of a call to .BR request_key (2). @@ -1249,7 +1249,7 @@ whose ID is specified in .IP The caller must have the appropriate authorization key. In other words, this operation is available only from a -.BR request-key (8)-style +.BR request\-key (8)-style program. See .BR request_key (2). @@ -1258,7 +1258,7 @@ The caller must have the appropriate authorization key, and once the uninstantiated key has been instantiated, the authorization key is revoked. In other words, this operation is available only from a -.BR request-key (8)-style +.BR request\-key (8)-style program. See .BR request_key (2) @@ -1963,7 +1963,7 @@ you probably want to use the various library functions mentioned in the descriptions of individual operations above. .SH EXAMPLES The program below provide subset of the functionality of the -.BR request-key (8) +.BR request\-key (8) program provided by the .I keyutils package. @@ -1973,7 +1973,7 @@ the program records various information in a log file. As described in .BR request_key (2), the -.BR request-key (8) +.BR request\-key (8) program is invoked with command-line arguments that describe a key that is to be instantiated. The example program fetches and logs these arguments. @@ -1983,10 +1983,10 @@ and then instantiates that key. The following shell session demonstrates the use of this program. In the session, we compile the program and then use it to temporarily replace the standard -.BR request-key (8) +.BR request\-key (8) program. (Note that temporarily disabling the standard -.BR request-key (8) +.BR request\-key (8) program may not be safe on some systems.) While our example program is installed, we use the example program shown in diff --git a/man2/request_key.2 b/man2/request_key.2 index 2e88eb50d7..e28c11ded9 100644 --- a/man2/request_key.2 +++ b/man2/request_key.2 @@ -82,23 +82,23 @@ permission, or it may be one of the following special keyring IDs: .TP .B KEY_SPEC_THREAD_KEYRING This specifies the caller's thread-specific keyring (see -.BR thread-keyring (7)). +.BR thread\-keyring (7)). .TP .B KEY_SPEC_PROCESS_KEYRING This specifies the caller's process-specific keyring (see -.BR process-keyring (7)). +.BR process\-keyring (7)). .TP .B KEY_SPEC_SESSION_KEYRING This specifies the caller's session-specific keyring (see -.BR session-keyring (7)). +.BR session\-keyring (7)). .TP .B KEY_SPEC_USER_KEYRING This specifies the caller's UID-specific keyring (see -.BR user-keyring (7)). +.BR user\-keyring (7)). .TP .B KEY_SPEC_USER_SESSION_KEYRING This specifies the caller's UID-session keyring (see -.BR user-session-keyring (7)). +.BR user\-session\-keyring (7)). .PP When the .I dest_keyring @@ -132,28 +132,28 @@ since Linux 2.6.29). The thread-specific keyring .RB ( KEY_REQKEY_DEFL_THREAD_KEYRING ; see -.BR thread-keyring (7)). +.BR thread\-keyring (7)). .IP \(bu The process-specific keyring .RB ( KEY_REQKEY_DEFL_PROCESS_KEYRING ; see -.BR process-keyring (7)). +.BR process\-keyring (7)). .IP \(bu The session-specific keyring .RB ( KEY_REQKEY_DEFL_SESSION_KEYRING ; see -.BR session-keyring (7)). +.BR session\-keyring (7)). .IP \(bu The session keyring for the process's user ID .RB ( KEY_REQKEY_DEFL_USER_SESSION_KEYRING ; see -.BR user-session-keyring (7)). +.BR user\-session\-keyring (7)). This keyring is expected to always exist. .IP \(bu The UID-specific keyring .RB ( KEY_REQKEY_DEFL_USER_KEYRING ; see -.BR user-keyring (7)). +.BR user\-keyring (7)). This keyring is also expected to always exist. .\" mtk: Are there circumstances where the user sessions and UID-specific .\" keyrings do not exist? @@ -258,9 +258,9 @@ Internally, the kernel also records the PID of the process that called .RE .IP c) The kernel creates a process that executes a user-space service such as -.BR request-key (8) +.BR request\-key (8) with a new session keyring that contains a link to the authorization key, V. -.\" The request-key(8) program can be invoked in circumstances *other* than +.\" The request\-key(8) program can be invoked in circumstances *other* than .\" when triggered by request_key(2). For example, upcalls from places such .\" as the DNS resolver. .IP @@ -268,7 +268,7 @@ This program is supplied with the following command-line arguments: .RS .IP [0] 4 The string -.IR """/sbin/request-key""" . +.IR """/sbin/request\-key""" . .IP [1] The string .I """create""" @@ -356,7 +356,7 @@ to fail until it does. The purpose of this negatively instantiated key is to prevent (possibly different) processes making repeated requests (that require expensive -.BR request-key (8) +.BR request\-key (8) upcalls) for a key that can't (at the moment) be positively instantiated. .PP Once the key has been instantiated, the authorization key @@ -364,7 +364,7 @@ Once the key has been instantiated, the authorization key is revoked, and the destination keyring .RB ( KEY_SPEC_REQUESTOR_KEYRING ) is no longer accessible from the -.BR request-key (8) +.BR request\-key (8) program. .PP If a key is created, then\(emregardless of whether it is a valid key or @@ -458,13 +458,13 @@ The call specifies the session keyring as the target keyring. .PP In order to demonstrate this program, we first create a suitable entry in the file -.IR /etc/request-key.conf . +.IR /etc/request\-key.conf . .PP .in +4n .EX $ sudo sh # \fBecho 'create user mtk:* * /bin/keyctl instantiate %k %c %S' \e\fP - \fB> /etc/request-key.conf\fP + \fB> /etc/request\-key.conf\fP # \fBexit\fP .EE .in @@ -489,7 +489,7 @@ and the session keyring of the requestor (i.e., the caller of .BR request_key ()). See -.BR request-key.conf (5) +.BR request\-key.conf (5) for details of these .I % specifiers. @@ -502,7 +502,7 @@ to verify that the requested key has been instantiated: .EX $ \fB./t_request_key user mtk:key1 "Payload data"\fP $ \fBgrep \(aq2dddaf50\(aq /proc/keys\fP -2dddaf50 I--Q--- 1 perm 3f010000 1000 1000 user mtk:key1: 12 +2dddaf50 I\-\-Q\-\-\- 1 perm 3f010000 1000 1000 user mtk:key1: 12 .EE .in .PP diff --git a/man2/sigaction.2 b/man2/sigaction.2 index 294a96b63a..21d8b15b39 100644 --- a/man2/sigaction.2 +++ b/man2/sigaction.2 @@ -945,7 +945,7 @@ See for details on manipulating signal sets. .PP See -.BR signal-safety (7) +.BR signal\-safety (7) for a list of the async-signal-safe functions that can be safely called inside from inside a signal handler. .\" diff --git a/man2/signal.2 b/man2/signal.2 index c79349918c..dbe5baa5e2 100644 --- a/man2/signal.2 +++ b/man2/signal.2 @@ -140,7 +140,7 @@ is set to .BR SIG_IGN . .PP See -.BR signal-safety (7) +.BR signal\-safety (7) for a list of the async-signal-safe functions that can be safely called from inside a signal handler. .PP diff --git a/man2/socket.2 b/man2/socket.2 index 1d95f4080a..7908f4fc8f 100644 --- a/man2/socket.2 +++ b/man2/socket.2 @@ -146,7 +146,7 @@ T}:T{ .\" rds-tools: https://github.com/oracle/rds-tools/blob/master/rds-rdma.7 .BR rds (7) .br -.BR rds-rdma (7) +.BR rds\-rdma (7) T} T{ .B AF_PPPOX |