mirror of https://github.com/mkerrisk/man-pages
Formatting fixes
This commit is contained in:
parent
b5cc2ffbaa
commit
4d52e8f81c
|
@ -147,7 +147,7 @@ The
|
|||
.BR poll ()
|
||||
system call was introduced in Linux 2.1.23.
|
||||
The
|
||||
.BR poll()
|
||||
.BR poll ()
|
||||
library call was introduced in libc 5.4.28
|
||||
(and provides emulation using select if your kernel does not
|
||||
have a poll syscall).
|
||||
|
|
|
@ -75,7 +75,7 @@ PTRACE_TRACEME
|
|||
Indicates that this process is to be traced by its parent. Any signal
|
||||
(except SIGKILL) delivered to this process will cause it to stop and its
|
||||
parent to be notified via
|
||||
.BR wait() .
|
||||
.BR wait ().
|
||||
Also, all subsequent calls to
|
||||
.BR exec ()
|
||||
by this process will cause a SIGTRAP to be sent to it, giving the parent a
|
||||
|
|
|
@ -117,7 +117,7 @@ via a prior call to
|
|||
(so that the default disposition for these signals does not occur if they
|
||||
are delivered between successive calls to
|
||||
.BR sigwaitinfo () or
|
||||
.BR sigtimedwait())
|
||||
.BR sigtimedwait ())
|
||||
and does not establish handlers for these signals.
|
||||
.PP
|
||||
POSIX leaves the meaning of a
|
||||
|
|
|
@ -358,7 +358,7 @@ The symbols RTLD_DEFAULT and RTLD_NEXT are defined by
|
|||
only when _GNU_SOURCE was defined before including it.
|
||||
.\" .LP
|
||||
.\" The string returned by
|
||||
.\" .BR dlerror()
|
||||
.\" .BR dlerror ()
|
||||
.\" should not be modified. Some systems give the prototype as
|
||||
.\" .sp
|
||||
.\" .in +5
|
||||
|
|
|
@ -26,7 +26,7 @@ the return value from the function is the number of group IDs
|
|||
actually stored. The group
|
||||
.I group
|
||||
is automatically included in the list of groups returned by
|
||||
.BR getgroup\%list() .
|
||||
.BR getgrouplist ().
|
||||
.SH "RETURN VALUE"
|
||||
If
|
||||
.RI * ngroups
|
||||
|
|
|
@ -119,9 +119,9 @@ or
|
|||
.B EOF
|
||||
on end of file or error.
|
||||
.PP
|
||||
.BR gets()
|
||||
.BR gets ()
|
||||
and
|
||||
.BR fgets()
|
||||
.BR fgets ()
|
||||
return
|
||||
.I s
|
||||
on success, and
|
||||
|
|
|
@ -160,7 +160,7 @@ as returned from one of the calls to
|
|||
.BR opendir (),
|
||||
.BR readdir (),
|
||||
or
|
||||
.BR stat().
|
||||
.BR stat ().
|
||||
If
|
||||
.I errfunc
|
||||
returns non-zero, or if
|
||||
|
|
|
@ -66,7 +66,7 @@ functions can be used as the comparison function
|
|||
The former sorts directory entries using
|
||||
.BR strcoll (3),
|
||||
the latter using
|
||||
.BR strvers\%cmp (3)
|
||||
.BR strverscmp (3)
|
||||
on the strings \fI(*a)\->d_name\fP and \fI(*b)\->d_name\fP.
|
||||
.SH "RETURN VALUE"
|
||||
The \fBscandir\fP() function returns the number of directory entries
|
||||
|
|
|
@ -71,7 +71,7 @@ and
|
|||
representation, respectively.
|
||||
|
||||
The expected form of the (initial portion of the) string is
|
||||
optional leading white space as recognized by \fIis\%space\fP(3),
|
||||
optional leading white space as recognized by \fIisspace\fP(3),
|
||||
an optional plus (``+'') or minus sign (``\-'') and then either
|
||||
(i) a decimal number, or (ii) a hexadecimal number,
|
||||
or (iii) an infinity, or (iv) a NAN (not-a-number).
|
||||
|
|
|
@ -60,7 +60,7 @@ parameter, must be the same while parsing the same string.
|
|||
.\" .SH EXAMPLE
|
||||
.\" The following parses words out of a string, using 'white space'
|
||||
.\" separators, with
|
||||
.\" .BR strtok_r() :
|
||||
.\" .BR strtok_r () :
|
||||
.\" .PP
|
||||
.\" .nf
|
||||
.\" char buf[128];
|
||||
|
|
|
@ -76,7 +76,7 @@ See
|
|||
The four functions \fIgetc_unlocked\fP(), \fIgetchar_unlocked\fP(),
|
||||
\fIputc_unlocked\fP(), \fIputchar_unlocked\fP() are in POSIX.1.
|
||||
The nonstandard
|
||||
.BR *_unlocked()
|
||||
.BR *_unlocked ()
|
||||
variants occur on a few Unix systems, and are available in recent glibc.
|
||||
.\" E.g., in HPUX 10.0. In HPUX 10.30 they are called obsolescent, and
|
||||
.\" moved to a compatibility library.
|
||||
|
|
|
@ -347,7 +347,7 @@ a previous event's processing). Suppose you receive 100 events from
|
|||
.BR epoll_wait (2),
|
||||
and in event #47 a condition causes event #13 to be closed.
|
||||
If you remove the structure and
|
||||
.BR close()
|
||||
.BR close ()
|
||||
the fd for event #13, then your
|
||||
event cache might still say there are events waiting for that fd causing
|
||||
confusion.
|
||||
|
|
Loading…
Reference in New Issue