mirror of https://github.com/mkerrisk/man-pages
s/the the/the/
This commit is contained in:
parent
05461740b0
commit
8c45053412
|
@ -225,7 +225,7 @@ on a file region, but only one process may hold a write lock
|
|||
both shared and exclusive.
|
||||
A single process can hold only one type of lock on a file region;
|
||||
if a new lock is applied to an already-locked region,
|
||||
then the existing lock is converted to the the new lock type.
|
||||
then the existing lock is converted to the new lock type.
|
||||
(Such conversions may involve splitting, shrinking, or coalescing with
|
||||
an existing lock if the byte range specified by the new lock does not
|
||||
precisely coincide with the range of the existing lock.)
|
||||
|
|
|
@ -87,7 +87,7 @@ appeared in kernel 2.5.60.
|
|||
Under Linux, \fBPOSIX_FADV_NORMAL\fP sets the readahead window to the
|
||||
default size for the backing device; \fBPOSIX_FADV_SEQUENTIAL\fP doubles
|
||||
this size, and \fBPOSIX_FADV_RANDOM\fP disables file readahead entirely.
|
||||
These changes affect the the entire file, not just the specified region
|
||||
These changes affect the entire file, not just the specified region
|
||||
(but other open file handles to the same file are unaffected).
|
||||
|
||||
\fBPOSIX_FADV_WILLNEED\fP and \fBPOSIX_FADV_NOREUSE\fP both initiate a
|
||||
|
|
|
@ -32,7 +32,7 @@ sigreturn \- return from signal handler and cleanup stack frame
|
|||
When the Linux kernel creates the stack frame for a signal handler, a
|
||||
call to
|
||||
.B sigreturn
|
||||
is inserted into the stack frame so that the the signal handler will
|
||||
is inserted into the stack frame so that the signal handler will
|
||||
call
|
||||
.B sigreturn
|
||||
upon return. This inserted call to
|
||||
|
|
Loading…
Reference in New Issue