mirror of https://github.com/mkerrisk/man-pages
Remove/replace extraneous .sp macros.
This commit is contained in:
parent
984886049d
commit
ca92ce95a3
20
man2/fcntl.2
20
man2/fcntl.2
|
@ -82,9 +82,9 @@ and make it be a copy of
|
||||||
This is different from
|
This is different from
|
||||||
.BR dup2 (2)
|
.BR dup2 (2)
|
||||||
which uses exactly the descriptor specified.
|
which uses exactly the descriptor specified.
|
||||||
.sp
|
.IP
|
||||||
On success, the new descriptor is returned.
|
On success, the new descriptor is returned.
|
||||||
.sp
|
.IP
|
||||||
See
|
See
|
||||||
.BR dup (2)
|
.BR dup (2)
|
||||||
for further details.
|
for further details.
|
||||||
|
@ -138,7 +138,7 @@ Duplicated file descriptors
|
||||||
.BR fork (2),
|
.BR fork (2),
|
||||||
etc.) refer to the same open file description, and thus
|
etc.) refer to the same open file description, and thus
|
||||||
share the same file status flags.
|
share the same file status flags.
|
||||||
.sp
|
|
||||||
The file status flags and their semantics are described in
|
The file status flags and their semantics are described in
|
||||||
.BR open (2).
|
.BR open (2).
|
||||||
.TP
|
.TP
|
||||||
|
@ -444,7 +444,7 @@ is subject to the same permissions checks as are described for
|
||||||
where the sending process is the one that employs
|
where the sending process is the one that employs
|
||||||
.B F_SETOWN
|
.B F_SETOWN
|
||||||
(but see BUGS below).
|
(but see BUGS below).
|
||||||
.sp
|
|
||||||
If the file descriptor
|
If the file descriptor
|
||||||
.I fd
|
.I fd
|
||||||
refers to a socket,
|
refers to a socket,
|
||||||
|
@ -542,7 +542,7 @@ Any other value (including
|
||||||
is the signal to send instead, and in this case additional info
|
is the signal to send instead, and in this case additional info
|
||||||
is available to the signal handler if installed with
|
is available to the signal handler if installed with
|
||||||
.BR SA_SIGINFO .
|
.BR SA_SIGINFO .
|
||||||
.sp
|
|
||||||
Additionally, passing a nonzero value to
|
Additionally, passing a nonzero value to
|
||||||
.B F_SETSIG
|
.B F_SETSIG
|
||||||
changes the signal recipient from a whole process to a specific thread
|
changes the signal recipient from a whole process to a specific thread
|
||||||
|
@ -550,7 +550,7 @@ within a process.
|
||||||
See the description of
|
See the description of
|
||||||
.B F_SETOWN
|
.B F_SETOWN
|
||||||
for more details.
|
for more details.
|
||||||
.sp
|
|
||||||
By using
|
By using
|
||||||
.B F_SETSIG
|
.B F_SETSIG
|
||||||
with a nonzero value, and setting
|
with a nonzero value, and setting
|
||||||
|
@ -578,7 +578,7 @@ should use the usual mechanisms
|
||||||
with
|
with
|
||||||
.B O_NONBLOCK
|
.B O_NONBLOCK
|
||||||
set etc.) to determine which file descriptors are available for I/O.
|
set etc.) to determine which file descriptors are available for I/O.
|
||||||
.sp
|
|
||||||
By selecting a real time signal (value >=
|
By selecting a real time signal (value >=
|
||||||
.BR SIGRTMIN ),
|
.BR SIGRTMIN ),
|
||||||
multiple I/O events may be queued using the same signal numbers.
|
multiple I/O events may be queued using the same signal numbers.
|
||||||
|
@ -793,7 +793,7 @@ DN_ATTRIB The attributes of a file were changed
|
||||||
(In order to obtain these definitions, the
|
(In order to obtain these definitions, the
|
||||||
.B _GNU_SOURCE
|
.B _GNU_SOURCE
|
||||||
feature test macro must be defined.)
|
feature test macro must be defined.)
|
||||||
.sp
|
|
||||||
Directory notifications are normally "one-shot", and the application
|
Directory notifications are normally "one-shot", and the application
|
||||||
must re-register to receive further notifications.
|
must re-register to receive further notifications.
|
||||||
Alternatively, if
|
Alternatively, if
|
||||||
|
@ -813,7 +813,7 @@ To disable notification of all events, make an
|
||||||
call specifying
|
call specifying
|
||||||
.I arg
|
.I arg
|
||||||
as 0.
|
as 0.
|
||||||
.sp
|
|
||||||
Notification occurs via delivery of a signal.
|
Notification occurs via delivery of a signal.
|
||||||
The default signal is
|
The default signal is
|
||||||
.BR SIGIO ,
|
.BR SIGIO ,
|
||||||
|
@ -831,7 +831,7 @@ and the
|
||||||
field of this structure contains the file descriptor which
|
field of this structure contains the file descriptor which
|
||||||
generated the notification (useful when establishing notification
|
generated the notification (useful when establishing notification
|
||||||
on multiple directories).
|
on multiple directories).
|
||||||
.sp
|
|
||||||
Especially when using
|
Especially when using
|
||||||
.BR DN_MULTISHOT ,
|
.BR DN_MULTISHOT ,
|
||||||
a real time signal should be used for notification,
|
a real time signal should be used for notification,
|
||||||
|
|
|
@ -41,12 +41,12 @@ but can be used from user space.
|
||||||
.\" , given the following information
|
.\" , given the following information
|
||||||
.\" in addition to that given in
|
.\" in addition to that given in
|
||||||
.\" .BR outb (9).
|
.\" .BR outb (9).
|
||||||
.sp
|
|
||||||
You compile with \fB\-O\fP or \fB\-O2\fP or similar.
|
You compile with \fB\-O\fP or \fB\-O2\fP or similar.
|
||||||
The functions
|
The functions
|
||||||
are defined as inline macros, and will not be substituted in without
|
are defined as inline macros, and will not be substituted in without
|
||||||
optimization enabled, causing unresolved references at link time.
|
optimization enabled, causing unresolved references at link time.
|
||||||
.sp
|
|
||||||
You use
|
You use
|
||||||
.BR ioperm (2)
|
.BR ioperm (2)
|
||||||
or alternatively
|
or alternatively
|
||||||
|
|
|
@ -200,7 +200,7 @@ as the
|
||||||
socket option (see
|
socket option (see
|
||||||
.BR tcp (7)),
|
.BR tcp (7)),
|
||||||
with the difference that this flag can be set on a per-call basis.
|
with the difference that this flag can be set on a per-call basis.
|
||||||
.sp
|
|
||||||
Since Linux 2.6, this flag is also supported for UDP sockets, and informs
|
Since Linux 2.6, this flag is also supported for UDP sockets, and informs
|
||||||
the kernel to package all of the data sent in calls with this flag set
|
the kernel to package all of the data sent in calls with this flag set
|
||||||
into a single datagram which is only transmitted when a call is performed
|
into a single datagram which is only transmitted when a call is performed
|
||||||
|
|
|
@ -694,7 +694,7 @@ symbolic links.
|
||||||
These system calls supersede the older system calls
|
These system calls supersede the older system calls
|
||||||
which, except in the case of the "stat" calls,
|
which, except in the case of the "stat" calls,
|
||||||
have the same name without the "64" suffix.
|
have the same name without the "64" suffix.
|
||||||
.sp
|
|
||||||
On newer platforms that only have 64-bit file access and 32-bit uids
|
On newer platforms that only have 64-bit file access and 32-bit uids
|
||||||
(e.g., alpha, ia64, s390x) there are no *64 or *32 calls.
|
(e.g., alpha, ia64, s390x) there are no *64 or *32 calls.
|
||||||
Where the *64 and *32 calls exist, the other versions are obsolete.
|
Where the *64 and *32 calls exist, the other versions are obsolete.
|
||||||
|
|
|
@ -302,7 +302,7 @@ Otherwise, the elements of \fIargv\fP aren't really const, because we
|
||||||
permute them.
|
permute them.
|
||||||
We pretend they're const in the prototype to be
|
We pretend they're const in the prototype to be
|
||||||
compatible with other systems.
|
compatible with other systems.
|
||||||
.sp
|
|
||||||
On some older implementations,
|
On some older implementations,
|
||||||
.BR getopt ()
|
.BR getopt ()
|
||||||
was declared in
|
was declared in
|
||||||
|
|
|
@ -1088,7 +1088,7 @@ idle task, respectively.
|
||||||
.\" does not seem to be quite right (at least in 2.6.12)
|
.\" does not seem to be quite right (at least in 2.6.12)
|
||||||
The last value should be USER_HZ times the
|
The last value should be USER_HZ times the
|
||||||
second entry in the uptime pseudo-file.
|
second entry in the uptime pseudo-file.
|
||||||
.sp
|
|
||||||
In Linux 2.6 this line includes three additional columns:
|
In Linux 2.6 this line includes three additional columns:
|
||||||
.I iowait
|
.I iowait
|
||||||
\- time waiting for I/O to complete (since 2.5.41);
|
\- time waiting for I/O to complete (since 2.5.41);
|
||||||
|
@ -1096,7 +1096,7 @@ In Linux 2.6 this line includes three additional columns:
|
||||||
\- time servicing interrupts (since 2.6.0-test4);
|
\- time servicing interrupts (since 2.6.0-test4);
|
||||||
.I softirq
|
.I softirq
|
||||||
\- time servicing softirqs (since 2.6.0-test4).
|
\- time servicing softirqs (since 2.6.0-test4).
|
||||||
.sp
|
|
||||||
Since Linux 2.6.11, there is an eighth column,
|
Since Linux 2.6.11, there is an eighth column,
|
||||||
.I steal
|
.I steal
|
||||||
\- stolen time, which is the time spent in other operating systems when
|
\- stolen time, which is the time spent in other operating systems when
|
||||||
|
|
|
@ -124,11 +124,11 @@ Dates should be written in the form YYYY-MM-DD.
|
||||||
.TP
|
.TP
|
||||||
.I source
|
.I source
|
||||||
The source of the command, function, or system call.
|
The source of the command, function, or system call.
|
||||||
.sp
|
|
||||||
For those few \fIman-pages\fP pages in Sections 1 and 8,
|
For those few \fIman-pages\fP pages in Sections 1 and 8,
|
||||||
probably you just want to write
|
probably you just want to write
|
||||||
.IR GNU .
|
.IR GNU .
|
||||||
.sp
|
|
||||||
For system calls, just write
|
For system calls, just write
|
||||||
.IR "Linux" .
|
.IR "Linux" .
|
||||||
(An earlier practice was to write the version number
|
(An earlier practice was to write the version number
|
||||||
|
@ -136,15 +136,15 @@ of the kernel from which the manual page was being written/checked.
|
||||||
However, this was never done consistently, and so was
|
However, this was never done consistently, and so was
|
||||||
probably worse than including no version number.
|
probably worse than including no version number.
|
||||||
Henceforth, avoid including a version number.)
|
Henceforth, avoid including a version number.)
|
||||||
.sp
|
|
||||||
For library calls that are part of glibc or one of the
|
For library calls that are part of glibc or one of the
|
||||||
other common GNU libraries, just use
|
other common GNU libraries, just use
|
||||||
.IR "GNU C Library" ", " GNU ,
|
.IR "GNU C Library" ", " GNU ,
|
||||||
or an empty string.
|
or an empty string.
|
||||||
.sp
|
|
||||||
For Section 4 pages, use
|
For Section 4 pages, use
|
||||||
.IR "Linux" .
|
.IR "Linux" .
|
||||||
.sp
|
|
||||||
In cases of doubt, just write
|
In cases of doubt, just write
|
||||||
.IR Linux ", or " GNU .
|
.IR Linux ", or " GNU .
|
||||||
.TP
|
.TP
|
||||||
|
|
|
@ -41,7 +41,7 @@ released by the University of California at Berkeley.
|
||||||
This was the first Berkeley release that contained a TCP/IP
|
This was the first Berkeley release that contained a TCP/IP
|
||||||
stack and the sockets API.
|
stack and the sockets API.
|
||||||
4.2BSD was released in 1983.
|
4.2BSD was released in 1983.
|
||||||
.sp
|
|
||||||
Earlier major BSD releases included \fI3BSD\fP (1980), \fI4BSD\fP (1980),
|
Earlier major BSD releases included \fI3BSD\fP (1980), \fI4BSD\fP (1980),
|
||||||
and \fI4.1BSD\fP (1981).
|
and \fI4.1BSD\fP (1981).
|
||||||
.TP
|
.TP
|
||||||
|
@ -188,7 +188,7 @@ The standard is available online at
|
||||||
http://www.unix-systems.org/version3/ ,
|
http://www.unix-systems.org/version3/ ,
|
||||||
and the interfaces that it describes are also available in the Linux
|
and the interfaces that it describes are also available in the Linux
|
||||||
manual pages package under sections 1p and 3p (e.g., "man 3p open").
|
manual pages package under sections 1p and 3p (e.g., "man 3p open").
|
||||||
.sp
|
|
||||||
The standard defines two levels of conformance:
|
The standard defines two levels of conformance:
|
||||||
.IR "POSIX conformance" ,
|
.IR "POSIX conformance" ,
|
||||||
which is a baseline set of interfaces required of a conforming system;
|
which is a baseline set of interfaces required of a conforming system;
|
||||||
|
@ -201,27 +201,27 @@ XSI-conformant systems can be branded
|
||||||
(XSI conformance constitutes the
|
(XSI conformance constitutes the
|
||||||
.I "Single UNIX Specification version 3"
|
.I "Single UNIX Specification version 3"
|
||||||
.RI ( SUSv3 ).)
|
.RI ( SUSv3 ).)
|
||||||
.sp
|
|
||||||
The POSIX.1-2001 document is broken into four parts:
|
The POSIX.1-2001 document is broken into four parts:
|
||||||
.sp
|
|
||||||
.BR XBD :
|
.BR XBD :
|
||||||
Definitions, terms and concepts, header file specifications.
|
Definitions, terms and concepts, header file specifications.
|
||||||
.sp
|
|
||||||
.BR XSH :
|
.BR XSH :
|
||||||
Specifications of functions (i.e., system calls and library
|
Specifications of functions (i.e., system calls and library
|
||||||
functions in actual implementations).
|
functions in actual implementations).
|
||||||
.sp
|
|
||||||
.BR XCU :
|
.BR XCU :
|
||||||
Specifications of commands and utilities
|
Specifications of commands and utilities
|
||||||
(i.e., the area formerly described by POSIX.2).
|
(i.e., the area formerly described by POSIX.2).
|
||||||
.sp
|
|
||||||
.BR XRAT :
|
.BR XRAT :
|
||||||
Informative text on the other parts of the standard.
|
Informative text on the other parts of the standard.
|
||||||
.sp
|
|
||||||
POSIX.1-2001 is aligned with C99, so that all of the
|
POSIX.1-2001 is aligned with C99, so that all of the
|
||||||
library functions standardized in C99 are also
|
library functions standardized in C99 are also
|
||||||
standardized in POSIX.1-1001.
|
standardized in POSIX.1-1001.
|
||||||
.sp
|
|
||||||
Two Technical Corrigenda (minor fixes and improvements)
|
Two Technical Corrigenda (minor fixes and improvements)
|
||||||
of the original 2001 standard have occurred:
|
of the original 2001 standard have occurred:
|
||||||
TC1 in 2003 (referred to as
|
TC1 in 2003 (referred to as
|
||||||
|
|
|
@ -796,7 +796,7 @@ is returned.
|
||||||
Returns true (i.e.,
|
Returns true (i.e.,
|
||||||
.I value
|
.I value
|
||||||
is nonzero) if the inbound data stream is at the urgent mark.
|
is nonzero) if the inbound data stream is at the urgent mark.
|
||||||
.sp
|
|
||||||
If the
|
If the
|
||||||
.B SO_OOBINLINE
|
.B SO_OOBINLINE
|
||||||
socket option is set, and
|
socket option is set, and
|
||||||
|
@ -812,7 +812,7 @@ next read from the socket will return the bytes following
|
||||||
the urgent data (to actually read the urgent data requires the
|
the urgent data (to actually read the urgent data requires the
|
||||||
.B recv(MSG_OOB)
|
.B recv(MSG_OOB)
|
||||||
flag).
|
flag).
|
||||||
.sp
|
|
||||||
Note that a read never reads across the urgent mark.
|
Note that a read never reads across the urgent mark.
|
||||||
If an application is informed of the presence of urgent data via
|
If an application is informed of the presence of urgent data via
|
||||||
.BR select (2)
|
.BR select (2)
|
||||||
|
|
Loading…
Reference in New Issue