LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

ffix

This commit is contained in:
Michael Kerrisk 2007-07-18 20:24:30 +00:00
parent 7fa092c8ca
commit a8d5553785
24 changed files with 115 additions and 114 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
man2/execve.2
View File

@ -49,7 +49,7 @@ starting with a line of the form:
.in +0.5i
.nf
\fB#! \fIinterpreter \fR[optional-arg]
\fB#!\fP \fIinterpreter \fP[optional-arg]
.fi
.in
@ -57,14 +57,14 @@ For details of the latter case, see "Interpreter scripts" below.
\fIargv\fP is an array of argument strings passed to the new program.
\fIenvp\fP is an array of strings, conventionally of the form
\fBkey=value\fR, which are passed as environment to the new program.
\fBkey=value\fP, which are passed as environment to the new program.
Both \fIargv\fP and \fIenvp\fP must be terminated by a null pointer.
The argument vector and environment can be accessed by the
called program's main function, when it is defined as:
.in +0.5i
.nf
int main(int argc, char *argv[], char *envp[])\fR.
int main(int argc, char *argv[], char *envp[])
.fi
.in
@ -109,8 +109,8 @@ If the executable is a dynamically linked ELF executable, the
interpreter named in the PT_INTERP segment is used to load the needed
shared libraries.
This interpreter is typically
\fI/lib/ld-linux.so.1\fR for binaries linked with the
Linux libc 5, or \fI/lib/ld-linux.so.2\fR for binaries linked with the
\fI/lib/ld-linux.so.1\fP for binaries linked with the
Linux libc 5, or \fI/lib/ld-linux.so.2\fP for binaries linked with the
glibc 2.
All process attributes are preserved during an
@ -243,7 +243,7 @@ permission enabled and whose first line is of the form:
.in +0.5i
.nf
\fB#! \fIinterpreter \fR[optional-arg]
\fB#!\fP \fIinterpreter \fP[optional-arg]
.fi
.in
@ -261,7 +261,7 @@ will be invoked with the following arguments:
.in +0.5i
.nf
\fIinterpreter\fR [optional-arg] \fIfilename\fR arg...
\fIinterpreter\fP [optional-arg] \fIfilename\fP arg...
.fi
.in

2
man2/futex.2
View File

@ -95,7 +95,7 @@ the futex and executes the
operation.
.TP
.B FUTEX_WAKE
This operation wakes at most \fIval\fR
This operation wakes at most \fIval\fP
processes waiting on this futex address (ie. inside
.BR FUTEX_WAIT ).
The arguments

8
man2/get_thread_area.2
View File

@ -16,11 +16,11 @@ get_thread_area \- Get a Thread Local Storage (TLS) area
.BR get_thread_area ()
returns an entry in the current thread's Thread Local Storage (TLS) array.
The index of the entry corresponds to the value
of \fIu_info->entry_number\fR, passed in by the user.
of \fIu_info->entry_number\fP, passed in by the user.
If the value is in bounds,
.BR get_thread_area ()
copies the corresponding
TLS entry into the area pointed to by \fIu_info\fR.
TLS entry into the area pointed to by \fIu_info\fP.
.SH "RETURN VALUE"
.BR get_thread_area ()
returns 0 on success.
@ -30,10 +30,10 @@ appropriately.
.SH ERRORS
.TP
.B EFAULT
\fIu_info\fR is an invalid pointer.
\fIu_info\fP is an invalid pointer.
.TP
.B EINVAL
\fIu_info->entry_number\fR is out of bounds.
\fIu_info->entry_number\fP is out of bounds.
.SH VERSIONS
A version of
.BR get_thread_area ()

10
man2/io_cancel.2
View File

@ -7,7 +7,7 @@
.\" .if t .Sp
.\" .ne 5
.\" .PP
.\" \fB\\$1\fR
.\" \fB\\$1\fP
.\" .PP
.\" ..
.\" .de Sp \" Vertical space (when we can't use .PP)
@ -44,9 +44,9 @@ Link with \fI-laio\fP.
.BR io_cancel ()
attempts to cancel an asynchronous I/O operation previously submitted with
.BR io_submit (2).
\fIctx_id\fR is the AIO context ID of the operation to be canceled.
\fIctx_id\fP is the AIO context ID of the operation to be canceled.
If the AIO context is found, the event will be canceled and then copied
into the memory pointed to by \fIresult\fR without being placed
into the memory pointed to by \fIresult\fP without being placed
into the completion queue.
.SH "RETURN VALUE"
.PP
@ -56,13 +56,13 @@ on failure, it returns one of the errors listed under ERRORS.
.SH "ERRORS"
.TP
.B EINVAL
The AIO context specified by \fIctx_id\fR is invalid.
The AIO context specified by \fIctx_id\fP is invalid.
.TP
.B EFAULT
One of the data structures points to invalid data.
.TP
.B EAGAIN
The \fIiocb\fR specified was not canceled.
The \fIiocb\fP specified was not canceled.
.TP
.B ENOSYS
.BR io_cancel ()

6
man2/io_destroy.2
View File

@ -7,7 +7,7 @@
.\" .if t .Sp
.\" .ne 5
.\" .PP
.\" \fB\\$1\fR
.\" \fB\\$1\fP
.\" .PP
.\" ..
.\" .de Sp \" Vertical space (when we can't use .PP)
@ -44,7 +44,7 @@ removes the asynchronous I/O context from the list of
I/O contexts and then destroys it.
.BR io_destroy ()
can also cancel any outstanding asynchronous I/O
actions on \fIctx\fR and block on completion.
actions on \fIctx\fP and block on completion.
.SH "RETURN VALUE"
.PP
.BR io_destroy ()
@ -53,7 +53,7 @@ on failure, it returns one of the errors listed under ERRORS.
.SH "ERRORS"
.TP
.B EINVAL
The AIO context specified by \fIctx\fR is invalid.
The AIO context specified by \fIctx\fP is invalid.
.TP
.B EFAULT
The context pointed to is invalid.

21
man2/io_getevents.2
View File

@ -7,7 +7,7 @@
.\" .if t .Sp
.\" .ne 5
.\" .PP
.\" \fB\\$1\fR
.\" \fB\\$1\fP
.\" .PP
.\" ..
.\" .de Sp \" Vertical space (when we can't use .PP)
@ -43,29 +43,30 @@ Link with \fI-laio\fP.
.SH "DESCRIPTION"
.PP
.BR io_getevents ()
attempts to read at least \fImin_nr\fR events and
up to \fInr\fR events from the completion queue of the AIO context
specified by \fIctx_id\fR.
\fItimeout\fR specifies the amount of time to wait for events,
where a NULL timeout waits until at least \fImin_nr\fR events
attempts to read at least \fImin_nr\fP events and
up to \fInr\fP events from the completion queue of the AIO context
specified by \fIctx_id\fP.
\fItimeout\fP specifies the amount of time to wait for events,
where a NULL timeout waits until at least \fImin_nr\fP events
have been seen.
Note that \fItimeout\fR is relative and will be updated if not NULL
Note that \fItimeout\fP is relative and will be updated if not NULL
and the operation blocks.
.SH "RETURN VALUE"
.PP
On success,
.BR io_getevents ()
returns the number of events read: 0 if no events are
available or < \fImin_nr\fR if the \fItimeout\fR has elapsed;
available or < \fImin_nr\fP if the \fItimeout\fP has elapsed;
on failure, it returns one of the errors listed under ERRORS.
.SH "ERRORS"
.TP
.B EINVAL
\fIctx_id\fR is invalid. \fImin_nr\fR is out of range or \fInr\fR is
\fIctx_id\fP is invalid.
\fImin_nr\fP is out of range or \fInr\fP is
out of range.
.TP
.B EFAULT
Either \fIevents\fR or \fItimeout\fR is an invalid pointer.
Either \fIevents\fP or \fItimeout\fP is an invalid pointer.
.TP
.B ENOSYS
.BR io_getevents ()

16
man2/io_setup.2
View File

@ -7,7 +7,7 @@
.\" .if t .Sp
.\" .ne 5
.\" .PP
.\" \fB\\$1\fR
.\" \fB\\$1\fP
.\" .PP
.\" ..
.\" .de Sp \" Vertical space (when we can't use .PP)
@ -41,10 +41,10 @@ Link with \fI-laio\fP.
.PP
.BR io_setup ()
creates an asynchronous I/O context capable of receiving
at least \fInr_events\fR.
\fIctxp\fR must not point to an AIO context that already exists, and must
at least \fInr_events\fP.
\fIctxp\fP must not point to an AIO context that already exists, and must
be initialized to 0 prior to the call.
On successful creation of the AIO context, \fI*ctxp\fR is filled in
On successful creation of the AIO context, \fI*ctxp\fP is filled in
with the resulting handle.
.SH "RETURN VALUE"
.PP
@ -54,17 +54,17 @@ on failure, it returns one of the errors listed under ERRORS.
.SH "ERRORS"
.TP
.B EINVAL
\fIctxp\fR is not initialized, or the specified \fInr_events\fR
exceeds internal limits. \fInr_events\fR should be greater than 0.
\fIctxp\fP is not initialized, or the specified \fInr_events\fP
exceeds internal limits. \fInr_events\fP should be greater than 0.
.TP
.B EFAULT
An invalid pointer is passed for \fIctxp\fR.
An invalid pointer is passed for \fIctxp\fP.
.TP
.B ENOMEM
Insufficient kernel resources are available.
.TP
.B EAGAIN
The specified \fInr_events\fR exceeds the user's limit of available events.
The specified \fInr_events\fP exceeds the user's limit of available events.
.TP
.B ENOSYS
.BR io_setup ()

26
man2/io_submit.2
View File

@ -7,7 +7,7 @@
.\" .if t .Sp
.\" .ne 5
.\" .PP
.\" \fB\\$1\fR
.\" \fB\\$1\fP
.\" .PP
.\" ..
.\" .de Sp \" Vertical space (when we can't use .PP)
@ -41,34 +41,34 @@ Link with \fI-laio\fP.
.SH "DESCRIPTION"
.PP
.BR io_submit ()
queues \fInr\fR I/O request blocks for processing in
the AIO context \fIctx_id\fR. \fIiocbpp\fR should be an array of
\fInr\fR AIO request blocks,
which will be submitted to context \fIctx_id\fR.
queues \fInr\fP I/O request blocks for processing in
the AIO context \fIctx_id\fP.
\fIiocbpp\fP should be an array of \fInr\fP AIO request blocks,
which will be submitted to context \fIctx_id\fP.
.SH "RETURN VALUE"
.PP
On success,
.BR io_submit ()
returns the number of \fIiocb\fRs submitted (which may be
0 if \fInr\fR is zero);
returns the number of \fIiocb\fPs submitted (which may be
0 if \fInr\fP is zero);
on failure, it returns one of the errors listed under ERRORS.
.SH "ERRORS"
.TP
.B EINVAL
The \fIaio_context\fR specified by \fIctx_id\fR is invalid.
\fInr\fR is less than 0.
The \fIiocb\fR at *iocbpp[0] is not properly initialized,
The \fIaio_context\fP specified by \fIctx_id\fP is invalid.
\fInr\fP is less than 0.
The \fIiocb\fP at *iocbpp[0] is not properly initialized,
or the operation specified is invalid for the file descriptor
in the \fIiocb\fR.
in the \fIiocb\fP.
.TP
.B EFAULT
One of the data structures points to invalid data.
.TP
.B EBADF
The file descriptor specified in the first \fIiocb\fR is invalid.
The file descriptor specified in the first \fIiocb\fP is invalid.
.TP
.B EAGAIN
Insufficient resources are available to queue any \fIiocb\fRs.
Insufficient resources are available to queue any \fIiocb\fPs.
.TP
.B ENOSYS
.BR io_submit ()

2
man2/mprotect.2
View File

@ -91,7 +91,7 @@ to mark it
The memory cannot be accessed.
.TP
.B EINVAL
\fIaddr\fR is not a valid pointer,
\fIaddr\fP is not a valid pointer,
or not a multiple of the system page size.
.\" Or: both PROT_GROWSUP and PROT_GROWSDOWN were specified in 'prot'.
.TP

22
man2/mremap.2
View File

@ -43,15 +43,15 @@ mremap \- re-map a virtual memory address
.SH DESCRIPTION
.BR mremap ()
expands (or shrinks) an existing memory mapping, potentially
moving it at the same time (controlled by the \fIflags\fR argument and
moving it at the same time (controlled by the \fIflags\fP argument and
the available virtual address space).
\fIold_address\fR is the old address of the virtual memory block that you
\fIold_address\fP is the old address of the virtual memory block that you
want to expand (or shrink).
Note that \fIold_address\fR has to be page
aligned. \fIold_size\fR is the old size of the
Note that \fIold_address\fP has to be page
aligned. \fIold_size\fP is the old size of the
virtual memory block.
\fInew_size\fR is the requested size of the
\fInew_size\fP is the requested size of the
virtual memory block after the resize.
In Linux the memory is divided into pages.
@ -74,7 +74,7 @@ mapping between virtual addresses and memory pages.
This can be used to implement a very efficient
.BR realloc (3).
The \fIflags\fR bit-mask argument may be 0, or include the following flag:
The \fIflags\fP bit-mask argument may be 0, or include the following flag:
.TP
.B MREMAP_MAYMOVE
By default, if there is not sufficient space to expand a mapping
@ -126,7 +126,7 @@ returns a pointer to the new virtual memory area.
On error, the value
.B MAP_FAILED
(that is, \fB(void *) \-1)\fP is returned,
and \fIerrno\fR is set appropriately.
and \fIerrno\fP is set appropriately.
.SH ERRORS
.TP
.B EAGAIN
@ -146,7 +146,7 @@ whole address space requested, but those mappings are of different types.
.TP
.B EINVAL
An invalid argument was given.
Possible causes are: \fIold_address\fR was not
Possible causes are: \fIold_address\fP was not
page aligned; a value other than
.B MREMAP_MAYMOVE
or
@ -203,6 +203,6 @@ argument.
.BR feature_test_macros (7)
.P
Your favorite OS text book for more information on paged memory.
(\fIModern Operating Systems\fR by Andrew S. Tannenbaum,
\fIInside Linux\fR by Randolf Bentson,
\fIThe Design of the UNIX Operating System\fR by Maurice J. Bach.)
(\fIModern Operating Systems\fP by Andrew S. Tannenbaum,
\fIInside Linux\fP by Randolf Bentson,
\fIThe Design of the UNIX Operating System\fP by Maurice J. Bach.)

10
man2/nanosleep.2
View File

@ -46,7 +46,7 @@ delays the execution of the program for at least the time specified in
.IR *req .
The function can return earlier if a signal has been delivered to the
process.
In this case, it returns \-1, sets \fIerrno\fR to
In this case, it returns \-1, sets \fIerrno\fP to
.BR EINTR ,
and writes the
remaining time into the structure pointed to by
@ -104,7 +104,7 @@ Problem with copying information from user space.
The pause has been interrupted by a non-blocked signal that was
delivered to the process.
The remaining sleep time has been written
into *\fIrem\fR so that the process can easily call
into *\fIrem\fP so that the process can easily call
.BR nanosleep ()
again and continue with the pause.
.TP
@ -120,7 +120,7 @@ POSIX.1-2001.
The current implementation of
.BR nanosleep ()
is based on the normal kernel timer mechanism, which has a resolution
of 1/\fIHZ\fR\ s (see
of 1/\fIHZ\fP\ s (see
.BR time (7)).
Therefore,
.BR nanosleep ()
@ -128,8 +128,8 @@ pauses always for at least the specified time, however it can take up
to 10 ms longer than specified until the process becomes runnable
again.
For the same reason, the value returned in case of a delivered
signal in *\fIrem\fR is usually rounded to the next larger multiple of
1/\fIHZ\fR\ s.
signal in *\fIrem\fP is usually rounded to the next larger multiple of
1/\fIHZ\fP\ s.
.SS "Old behavior"
In order to support applications requiring much more precise pauses
(e.g., in order to control some time-critical hardware),

14
man2/open.2
View File

@ -179,7 +179,7 @@ is described in
.BR raw (8).
.TP
.B O_DIRECTORY
If \fIpathname\fR is not a directory, cause the open to fail.
If \fIpathname\fP is not a directory, cause the open to fail.
.\" But see the following and its replies:
.\" http://marc.theaimsgroup.com/?t=112748702800001&r=1&w=2
.\" [PATCH] open: O_DIRECTORY and O_CREAT together should fail
@ -256,13 +256,13 @@ refers to a terminal device \(em see
process does not have one.
.TP
.B O_NOFOLLOW
If \fIpathname\fR is a symbolic link, then the open fails.
If \fIpathname\fP is a symbolic link, then the open fails.
This is a FreeBSD extension, which was added to Linux in version 2.1.126.
Symbolic links in earlier components of the pathname will still be
followed.
.\" The headers from glibc 2.0.100 and later include a
.\" definition of this flag; \fIkernels before 2.1.126 will ignore it if
.\" used\fR.
.\" used\fP.
.TP
.BR O_NONBLOCK " or " O_NDELAY
When possible, the file is opened in non-blocking mode.
@ -424,7 +424,7 @@ is set).
.B ELOOP
Too many symbolic links were encountered in resolving
.IR pathname ,
or \fBO_NOFOLLOW\fR was specified but
or \fBO_NOFOLLOW\fP was specified but
.I pathname
was a symbolic link.
.TP
@ -464,7 +464,7 @@ has no room for the new file.
.B ENOTDIR
A component used as a directory in
.I pathname
is not, in fact, a directory, or \fBO_DIRECTORY\fR was specified and
is not, in fact, a directory, or \fBO_DIRECTORY\fP was specified and
.I pathname
was not a directory.
.TP
@ -548,8 +548,8 @@ amongst others
.BR O_SYNC " and " O_NDELAY .
POSIX provides for three different variants of synchronized I/O,
corresponding to the flags \fBO_SYNC\fR, \fBO_DSYNC\fR and
\fBO_RSYNC\fR.
corresponding to the flags \fBO_SYNC\fP, \fBO_DSYNC\fP and
\fBO_RSYNC\fP.
Currently (2.1.130) these are all synonymous under Linux.
Note that

4
man2/readv.2
View File

@ -145,7 +145,7 @@ The sum of the
values overflows an
.I ssize_t
value.
Or, the vector count \fIiovcnt\fR is less than zero or greater than the
Or, the vector count \fIiovcnt\fP is less than zero or greater than the
permitted maximum.
.SH "CONFORMING TO"
4.4BSD (the
@ -153,7 +153,7 @@ permitted maximum.
and
.BR writev ()
functions first appeared in 4.2BSD), POSIX.1-2001.
Linux libc5 used \fIsize_t\fR as the type of the \fIiovcnt\fR parameter,
Linux libc5 used \fIsize_t\fP as the type of the \fIiovcnt\fP parameter,
and \fIint\fP as return type for these functions.
.\" The readv/writev system calls were buggy before Linux 1.3.40.
.\" (Says release.libc.)

14
man2/sched_get_priority_max.2
View File

@ -39,11 +39,11 @@ sched_get_priority_max, sched_get_priority_min \- get static priority range
.SH DESCRIPTION
.BR sched_get_priority_max ()
returns the maximum priority value that can be used with the
scheduling algorithm identified by \fIpolicy\fR.
scheduling algorithm identified by \fIpolicy\fP.
.BR sched_get_priority_min ()
returns the minimum priority value that can be used with the
scheduling algorithm identified by \fIpolicy\fR.
Supported \fIpolicy\fR
scheduling algorithm identified by \fIpolicy\fP.
Supported \fIpolicy\fP
values are
.BR SCHED_FIFO ,
.BR SCHED_RR ,
@ -63,8 +63,8 @@ value returned by
.BR sched_get_priority_min ().
Linux allows the static priority value range 1 to 99 for
\fBSCHED_FIFO\fR and \fBSCHED_RR\fR and the priority 0 for
\fBSCHED_OTHER\fR and \fBSCHED_BATCH\fP.
\fBSCHED_FIFO\fP and \fBSCHED_RR\fP and the priority 0 for
\fBSCHED_OTHER\fP and \fBSCHED_BATCH\fP.
Scheduling priority ranges for the various policies
are not alterable.
@ -75,7 +75,7 @@ priority range and map it to the interval given by
and
.BR sched_get_priority_min ().
POSIX.1-2001 requires a spread of at least 32 between the maximum and the
minimum values for \fBSCHED_FIFO\fR and \fBSCHED_RR\fR.
minimum values for \fBSCHED_FIFO\fP and \fBSCHED_RR\fP.
POSIX systems on which
.BR sched_get_priority_max ()
@ -97,7 +97,7 @@ is set appropriately.
.SH ERRORS
.TP
.B EINVAL
The parameter \fIpolicy\fR does not identify a defined scheduling policy.
The parameter \fIpolicy\fP does not identify a defined scheduling policy.
.SH "CONFORMING TO"
POSIX.1-2001.
.SH "SEE ALSO"

12
man2/sched_rr_get_interval.2
View File

@ -36,10 +36,10 @@ sched_rr_get_interval \- get the SCHED_RR interval for the named process
.BI "int sched_rr_get_interval(pid_t " pid ", struct timespec * " tp );
.SH DESCRIPTION
.BR sched_rr_get_interval ()
writes into the \fItimespec\fR structure pointed to by \fItp\fR the
round-robin time quantum for the process identified by \fIpid\fR.
writes into the \fItimespec\fP structure pointed to by \fItp\fP the
round-robin time quantum for the process identified by \fIpid\fP.
The \fItimespec\fR structure has the following form:
The \fItimespec\fP structure has the following form:
.in +0.5i
.nf
@ -51,8 +51,8 @@ struct timespec {
.in
If
\fIpid\fR is zero, the time quantum for the calling process is written
into *\fItp\fR.
\fIpid\fP is zero, the time quantum for the calling process is written
into *\fItp\fP.
The identified process should be running under the
.B SCHED_RR
scheduling policy.
@ -84,7 +84,7 @@ Invalid pid.
The system call is not yet implemented (only on rather old kernels).
.TP
.B ESRCH
The process whose ID is \fIpid\fR could not be found.
The process whose ID is \fIpid\fP could not be found.
.SH "CONFORMING TO"
POSIX.1-2001.
.SH NOTES

2
man2/sched_setaffinity.2
View File

@ -165,7 +165,7 @@ or it must possess the
capability.
.TP
.B ESRCH
The process whose ID is \fIpid\fR could not be found.
The process whose ID is \fIpid\fP could not be found.
.SH VERSIONS
The CPU affinity system calls were introduced in Linux kernel 2.5.8.
The library interfaces were introduced in glibc 2.3.

18
man2/sched_setparam.2
View File

@ -48,11 +48,11 @@ sched_setparam, sched_getparam \- set and get scheduling parameters
.SH DESCRIPTION
.BR sched_setparam ()
sets the scheduling parameters associated with the scheduling policy
for the process identified by \fIpid\fR.
If \fIpid\fR is zero, then
for the process identified by \fIpid\fP.
If \fIpid\fP is zero, then
the parameters of the current process are set.
The interpretation of
the parameter \fIparam\fR depends on the scheduling
the parameter \fIparam\fP depends on the scheduling
policy of the process identified by
.IR pid .
See
@ -61,14 +61,14 @@ for a description of the scheduling policies supported under Linux.
.BR sched_getparam ()
retrieves the scheduling parameters for the
process identified by \fIpid\fR.
If \fIpid\fR is zero, then the parameters
process identified by \fIpid\fP.
If \fIpid\fP is zero, then the parameters
of the current process are retrieved.
.BR sched_setparam ()
checks the validity of \fIparam\fR for the scheduling policy of the
checks the validity of \fIparam\fP for the scheduling policy of the
process.
The parameter \fIparam->sched_priority\fR must lie within the
The parameter \fIparam->sched_priority\fP must lie within the
range given by
.BR sched_get_priority_min (2)
and
@ -97,7 +97,7 @@ is set appropriately.
.SH ERRORS
.TP
.B EINVAL
The parameter \fIparam\fR does not make sense for the current
The parameter \fIparam\fP does not make sense for the current
scheduling policy.
.TP
.B EPERM
@ -107,7 +107,7 @@ The calling process does not have appropriate privileges
capability).
.TP
.B ESRCH
The process whose ID is \fIpid\fR could not be found.
The process whose ID is \fIpid\fP could not be found.
.SH "CONFORMING TO"
POSIX.1-2001.
.SH "SEE ALSO"

4
man2/set_thread_area.2
View File

@ -45,10 +45,10 @@ set appropriately.
.SH "ERRORS"
.TP
.B EINVAL
\fIu_info->entry_number\fR is out of bounds.
\fIu_info->entry_number\fP is out of bounds.
.TP
.B EFAULT
\fIu_info\fR is an invalid pointer.
\fIu_info\fP is an invalid pointer.
.TP
.B ESRCH
A free TLS entry could not be located.

2
man2/umask.2
View File

@ -52,7 +52,7 @@ and other system calls that create files
.\" but NOT the System V IPC *get() calls
to modify the permissions placed on newly created files or directories.
Specifically, permissions in the umask are turned off from
the \fImode\fR argument to
the \fImode\fP argument to
.BR open (2)
and
.BR mkdir (2).

2
man2/wait.2
View File

@ -173,7 +173,7 @@ is not NULL,
.BR wait ()
and
.BR waitpid ()
store status information in the \fIint\fR to which it points.
store status information in the \fIint\fP to which it points.
This integer can be inspected with the following macros (which
take the integer itself as an argument, not a pointer to it,
as is done in

12
man3/errno.3
View File

@ -51,13 +51,13 @@ one has to zero
.I errno
before the call in order to detect possible errors.
\fIerrno\fR is defined by the ISO C standard to be a modifiable lvalue
of type \fIint\fR, and must not be explicitly declared; \fIerrno\fR
\fIerrno\fP is defined by the ISO C standard to be a modifiable lvalue
of type \fIint\fP, and must not be explicitly declared; \fIerrno\fP
may be a macro.
\fIerrno\fR is thread-local; setting it in one thread
\fIerrno\fP is thread-local; setting it in one thread
does not affect its value in any other thread.
Valid error numbers are all non-zero; \fIerrno\fR is never set to zero
Valid error numbers are all non-zero; \fIerrno\fP is never set to zero
by any library function.
All the error names specified by POSIX.1
must have distinct values, with the exception of
@ -68,8 +68,8 @@ which may be the same.
.\" The following is now
.\" POSIX.1 (2001 edition) lists the following symbolic error names. Of
.\" these, \fBEDOM\fR and \fBERANGE\fR are in the ISO C standard. ISO C
.\" Amendment 1 defines the additional error number \fBEILSEQ\fR for
.\" these, \fBEDOM\fP and \fBERANGE\fP are in the ISO C standard. ISO C
.\" Amendment 1 defines the additional error number \fBEILSEQ\fP for
.\" coding errors in multibyte or wide characters.
.\"
Below is a list of the symbolic error names that are defined on Linux.

2
man3/error.3
View File

@ -55,7 +55,7 @@ the program name, a colon and a space, the message specified by the
.BR printf (3)-style
format string \fIformat\fP, and, if \fIerrnum\fP is
non-zero, a second colon and a space followed by the string given by
\fBperror(\fIerrnum\fB)\fR.
\fBperror(\fIerrnum\fB)\fP.
Any arguments required for
.I format
should follow

4
man3/fopen.3
View File

@ -129,10 +129,10 @@ or
.BR fgetpos (3)
operation between write and read operations on such a stream.
This operation may be an apparent no-op
(as in \fIfseek(..., 0L, SEEK_CUR)\fR
(as in \fIfseek(..., 0L, SEEK_CUR)\fP
called for its synchronizing side effect.
.PP
Opening a file in append mode (\fBa\fR as the first character of
Opening a file in append mode (\fBa\fP as the first character of
.IR mode )
causes all subsequent write operations to this stream to occur
at end-of-file, as if preceded by an

2
man3/getspnam.3
View File

@ -209,7 +209,7 @@ struct spwd {
.SH "RETURN VALUE"
The functions that return a pointer return NULL if no more entries
are available or if an error occurs during processing.
The functions which have \fIint\fR as the return value return 0 for
The functions which have \fIint\fP as the return value return 0 for
success and \-1 for failure.
.LP
For the non-reentrant functions, the return value may point to static area,