mirror of https://github.com/mkerrisk/man-pages
Removed trailing white space at end of lines
This commit is contained in:
parent
31a1b45ece
commit
afa27faacf
|
@ -322,7 +322,7 @@ to exceed this limit yield the error
|
|||
on BSD.)
|
||||
|
||||
Since Linux 4.5,
|
||||
this limit also defines the maximum number of file descriptors that
|
||||
this limit also defines the maximum number of file descriptors that
|
||||
an unprivileged process (one without the
|
||||
.BR CAP_SYS_RESOURCE
|
||||
capability) may have "in flight" to other processes,
|
||||
|
|
|
@ -396,7 +396,7 @@ category, then it will not receive permissions granted in the
|
|||
category.
|
||||
|
||||
The
|
||||
.I possessor
|
||||
.I possessor
|
||||
category grants permissions that are cumulative with the grants from the
|
||||
.IR user ,
|
||||
.IR group ,
|
||||
|
@ -1992,6 +1992,6 @@ main(int argc, char *argv[])
|
|||
.BR request\-key (8)
|
||||
|
||||
The kernel source files
|
||||
.IR Documentation/security/keys.txt
|
||||
.IR Documentation/security/keys.txt
|
||||
and
|
||||
.IR Documentation/security/keys\-request\-key.txt .
|
||||
|
|
|
@ -144,7 +144,7 @@ The session-specific keyring
|
|||
see
|
||||
.BR session-keyring (7)).
|
||||
.IP \(bu
|
||||
The session keyring for the process's user ID
|
||||
The session keyring for the process's user ID
|
||||
.RB ( KEY_REQKEY_DEFL_USER_SESSION_KEYRING ;
|
||||
see
|
||||
.BR user-session-keyring (7)).
|
||||
|
|
|
@ -267,7 +267,7 @@ and
|
|||
can be used to refer to the caller's own instances of these keyrings.
|
||||
|
||||
A link to the user keyring is placed in a new session keyring by
|
||||
.BR pam_keyinit (8)
|
||||
.BR pam_keyinit (8)
|
||||
when a new login session is initiated.
|
||||
.TP
|
||||
Persistent keyrings
|
||||
|
@ -464,7 +464,7 @@ If a matching key is found that has an error state attached,
|
|||
that error state is noted and the search continues.
|
||||
.IP (6)
|
||||
If no valid matching key is found,
|
||||
then the first noted error state is returned; otherwise, an
|
||||
then the first noted error state is returned; otherwise, an
|
||||
.B ENOKEY
|
||||
error is returned.
|
||||
.P
|
||||
|
@ -521,7 +521,7 @@ The thread need not possess the key for it to be visible in this file.
|
|||
.\" David Howells, Dec 2016 linux-man@:
|
||||
.\" This [The thread need not possess the key for it to be visible in
|
||||
.\" this file.] is correct. See proc_keys_show() in security/keys/proc.c:
|
||||
.\"
|
||||
.\"
|
||||
.\" rc = key_task_permission(key_ref, ctx.cred, KEY_NEED_VIEW);
|
||||
.\" if (rc < 0)
|
||||
.\" return 0;
|
||||
|
|
|
@ -46,7 +46,7 @@ When performing buffered I/O on a file, the
|
|||
functions must maintain a statically allocated data buffer
|
||||
along with associated counters and indexes (or pointers)
|
||||
that record the amount of data and the current position in the buffer.
|
||||
Suppose that the main program is in the middle of a call to a
|
||||
Suppose that the main program is in the middle of a call to a
|
||||
.I stdio
|
||||
function such as
|
||||
.BR printf (3)
|
||||
|
@ -67,7 +67,7 @@ and
|
|||
with respect to global variables in the main program.
|
||||
.IP 2.
|
||||
Block signal delivery in the main program when calling functions
|
||||
that are unsafe or operating on global data that is also accessed
|
||||
that are unsafe or operating on global data that is also accessed
|
||||
by the signal handler.
|
||||
.PP
|
||||
Generally, the second choice is difficult in programs of any complexity,
|
||||
|
|
Loading…
Reference in New Issue