Removed trailing white space at end of lines

This commit is contained in:
Michael Kerrisk 2014-02-26 18:29:50 +01:00
parent 778fcac982
commit 92692952b1
5 changed files with 6 additions and 6 deletions

View File

@ -321,8 +321,8 @@ because UID mapping is done on the server and hidden from the client,
which checks permissions. (NFS versions 3 and higher perform the check on
the server.)
Similar problems can occur to FUSE mounts.
.\"
.\"
.\"
.\"
.SS faccessat ()
The raw
.BR faccessat ()

View File

@ -50,7 +50,7 @@ at which point the kernel does the real work of the system call; and
.IP *
setting
.I errno
if the system call returns an error number when the kernel returns the
if the system call returns an error number when the kernel returns the
CPU to user mode.
.LP
However, in a few cases, a wrapper function may do rather more than this,

View File

@ -247,7 +247,7 @@ SVr4, 4.4BSD, POSIX.1-2001 (but see below), POSIX.1-2008.
.\" The Linux version differs from the SVr4 version in that it
.\" does not require root permission to create pipes, also in that no
.\" EMULTIHOP, ENOLINK, or EINTR error is documented.
.BR mknodat ():
POSIX.1-2008.
.SH NOTES

View File

@ -1130,7 +1130,7 @@ and
.BR mkfifoat (3))
are supported
for two reasons.
Here, the explanation is in terms of the
Here, the explanation is in terms of the
.BR openat ()
call, but the rationale is the analogous for the other interfaces.

View File

@ -1930,7 +1930,7 @@ At the system call level, the
.BR PTRACE_PEEKTEXT ,
.BR PTRACE_PEEKDATA ,
and
.BR PTRACE_PEEKUSER
.BR PTRACE_PEEKUSER
requests have a different API: they store the result
at the address specified by the
.I data