mirror of https://github.com/mkerrisk/man-pages
Removed trailing white space at end of lines
This commit is contained in:
parent
83d5dd655c
commit
d5dd3a91dc
|
@ -673,7 +673,7 @@ Any other value (including
|
|||
is the signal to send instead, and in this case additional info
|
||||
is available to the signal handler if installed with
|
||||
.BR SA_SIGINFO .
|
||||
.\"
|
||||
.\"
|
||||
.\" The following was true only up until 2.6.11:
|
||||
.\"
|
||||
.\" Additionally, passing a nonzero value to
|
||||
|
|
|
@ -118,7 +118,7 @@ POSIX.1 does not specify all of possible ID changes that are permitted
|
|||
on Linux for an unprivileged process.
|
||||
For
|
||||
.BR setreuid (),
|
||||
the effective user ID can be made the same as the
|
||||
the effective user ID can be made the same as the
|
||||
real user ID or the save set-user-ID,
|
||||
and it is unspecified whether unprivileged processes may set the
|
||||
real user ID to the real user ID, the effective user ID, or the
|
||||
|
|
|
@ -88,7 +88,7 @@ Therefore, unless the application is strictly performing overwrites of
|
|||
already-instantiated disk blocks, there are no guarantees that the data will
|
||||
be available after a crash.
|
||||
There is no user interface to know if a write is purely an overwrite.
|
||||
On filesystem using copy-on-write semantics (e.g.,
|
||||
On filesystem using copy-on-write semantics (e.g.,
|
||||
.IR btrfs )
|
||||
an overwrite of existing allocated blocks is impossible.
|
||||
When writing into preallocated space,
|
||||
|
|
Loading…
Reference in New Issue