diff options
382 files changed, 1475 insertions, 1471 deletions
diff --git a/man3/CPU_SET.3 b/man3/CPU_SET.3 index 79e2b462b5..bb465c60bb 100644 --- a/man3/CPU_SET.3 +++ b/man3/CPU_SET.3 @@ -83,14 +83,14 @@ data structure represents a set of CPUs. CPU sets are used by .BR sched_setaffinity (2) and similar interfaces. - +.PP The .I cpu_set_t data type is implemented as a bit mask. However, the data structure treated as considered opaque: all manipulation of CPU sets should be done via the macros described in this page. - +.PP The following macros are provided to operate on the CPU set .IR set : .TP 17 @@ -139,7 +139,7 @@ The constant (currently 1024) specifies a value one greater than the maximum CPU number that can be stored in .IR cpu_set_t . - +.PP The following macros perform logical operations on CPU sets: .TP 17 .BR CPU_AND () @@ -182,7 +182,7 @@ size CPU sets (e.g., to allocate sets larger than that defined by the standard .I cpu_set_t data type), glibc nowadays provides a set of macros to support this. - +.PP The following macros are used to allocate and deallocate CPU sets: .TP 17 .BR CPU_ALLOC () @@ -219,27 +219,27 @@ return nonzero if is in .IR set ; otherwise, it returns 0. - +.PP .BR CPU_COUNT () and .BR CPU_COUNT_S () return the number of CPUs in .IR set . - +.PP .BR CPU_EQUAL () and .BR CPU_EQUAL_S () return nonzero if the two CPU sets are equal; otherwise they return 0. - +.PP .BR CPU_ALLOC () returns a pointer on success, or NULL on failure. (Errors are as for .BR malloc (3).) - +.PP .BR CPU_ALLOC_SIZE () returns the number of bytes required to store a CPU set of the specified cardinality. - +.PP The other functions do not return a value. .SH VERSIONS The @@ -249,10 +249,10 @@ The and .BR CPU_ISSET () macros were added in glibc 2.3.3. - +.PP .BR CPU_COUNT () first appeared in glibc 2.6. - +.PP .BR CPU_AND (), .BR CPU_OR (), .BR CPU_XOR (), @@ -275,14 +275,14 @@ These interfaces are Linux-specific. .SH NOTES To duplicate a CPU set, use .BR memcpy (3). - +.PP Since CPU sets are bit masks allocated in units of long words, the actual number of CPUs in a dynamically allocated CPU set will be rounded up to the next multiple of .IR "sizeof(unsigned long)" . An application should consider the contents of these extra bits to be undefined. - +.PP Notwithstanding the similarity in the names, note that the constant .B CPU_SETSIZE @@ -294,7 +294,7 @@ while the argument of the .BR CPU_*_S () macros is a size in bytes. - +.PP The data types for arguments and return values shown in the SYNOPSIS are hints what about is expected in each case. However, since these interfaces are implemented as macros, @@ -315,7 +315,7 @@ These bugs are fixed in glibc 2.9. .SH EXAMPLE The following program demonstrates the use of some of the macros used for dynamically allocated CPU sets. - +.PP .nf #define _GNU_SOURCE #include <sched.h> diff --git a/man3/INFINITY.3 b/man3/INFINITY.3 index 93900c1dc9..3e26d714f0 100644 --- a/man3/INFINITY.3 +++ b/man3/INFINITY.3 @@ -47,7 +47,7 @@ The macro expands to a .I float constant representing positive infinity. - +.PP The macro .B NAN expands to a @@ -62,7 +62,7 @@ The opposite is a .I signaling NaN. See IEC 60559:1989. - +.PP The macros .BR HUGE_VAL , .BR HUGE_VALF , diff --git a/man3/__ppc_get_timebase.3 b/man3/__ppc_get_timebase.3 index 0c998ca694..6c4fd6d1f9 100644 --- a/man3/__ppc_get_timebase.3 +++ b/man3/__ppc_get_timebase.3 @@ -39,7 +39,7 @@ reads the current value of the Time Base Register and returns its value, while .BR __ppc_get_timebase_freq () returns the frequency in which the Time Base Register is updated. - +.PP The Time Base Register is a 64-bit register provided by Power Architecture processors. It stores a monotonically incremented value that is updated at a @@ -49,7 +49,7 @@ frequency. .BR __ppc_get_timebase () returns a 64-bit unsigned integer that represents the current value of the Time Base Register. - +.PP .BR __ppc_get_timebase_freq () returns a 64-bit unsigned integer that represents the frequency at which the Time Base Register is updated. diff --git a/man3/__ppc_set_ppr_med.3 b/man3/__ppc_set_ppr_med.3 index af3982d13a..7616d7f1b6 100644 --- a/man3/__ppc_set_ppr_med.3 +++ b/man3/__ppc_set_ppr_med.3 @@ -129,5 +129,5 @@ Availability of these functions can be tested using .BR "#ifdef _ARCH_PWR8" . .SH SEE ALSO .BR __ppc_yield (3) - +.PP .IR "Power ISA, Book\ II - Section\ 3.1 (Program Priority Registers)" diff --git a/man3/__ppc_yield.3 b/man3/__ppc_yield.3 index f4b930a7f2..9a7103f529 100644 --- a/man3/__ppc_yield.3 +++ b/man3/__ppc_yield.3 @@ -80,5 +80,5 @@ T} Thread safety MT-Safe These functions are nonstandard GNU extensions. .SH SEE ALSO .BR __ppc_set_ppr_med (3) - +.PP .IR "Power ISA, Book\ II - Section\ 3.2 (""or"" architecture)" diff --git a/man3/__setfpucw.3 b/man3/__setfpucw.3 index 930090719e..cf5f168c10 100644 --- a/man3/__setfpucw.3 +++ b/man3/__setfpucw.3 @@ -50,7 +50,7 @@ macros from can be used. .SH EXAMPLE .B __setfpucw(0x1372) - +.PP Set FPU control word on the i386 architecture to .br \- extended precision diff --git a/man3/acos.3 b/man3/acos.3 index d4391b1fba..e241228e34 100644 --- a/man3/acos.3 +++ b/man3/acos.3 @@ -70,22 +70,22 @@ the value whose cosine is On success, these functions return the arc cosine of .IR x in radians; the return value is in the range [0,\ pi]. - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +1, +0 is returned. - +.PP If .I x is positive infinity or negative infinity, a domain error occurs, and a NaN is returned. - +.PP If .I x is outside the range [\-1,\ 1], @@ -122,7 +122,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/acosh.3 b/man3/acosh.3 index afc098f177..47d3350777 100644 --- a/man3/acosh.3 +++ b/man3/acosh.3 @@ -79,19 +79,19 @@ that is the value whose hyperbolic cosine is .SH RETURN VALUE On success, these functions return the inverse hyperbolic cosine of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +1, +0 is returned. - +.PP If .I x is positive infinity, positive infinity is returned. - +.PP If .I x is less than 1, @@ -128,7 +128,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/adjtime.3 b/man3/adjtime.3 index bd4c1b6343..a7698bed06 100644 --- a/man3/adjtime.3 +++ b/man3/adjtime.3 @@ -70,7 +70,7 @@ has been completed. If the adjustment in .I delta is negative, then the clock is slowed down in a similar fashion. - +.PP If a clock adjustment from an earlier .BR adjtime () call is already in progress @@ -80,7 +80,7 @@ call, and .I delta is not NULL for the later call, then the earlier adjustment is stopped, but any already completed part of that adjustment is not undone. - +.PP If .I olddelta is not NULL, then the buffer that it points to is used to return @@ -130,7 +130,7 @@ to adjust the time prevents the problems that can be caused for certain applications (e.g., .BR make (1)) by abrupt positive or negative jumps in the system time. - +.PP .BR adjtime () is intended to be used to make small adjustments to the system time. Most systems impose a limit on the adjustment that can be specified in diff --git a/man3/aio_fsync.3 b/man3/aio_fsync.3 index a3f10bfb33..251e73ec99 100644 --- a/man3/aio_fsync.3 +++ b/man3/aio_fsync.3 @@ -55,7 +55,7 @@ is .BR O_DSYNC , this call is the asynchronous analog of .BR fdatasync (2). - +.PP Note that this is a request only; it does not wait for I/O completion. .LP Apart from diff --git a/man3/aio_init.3 b/man3/aio_init.3 index 2e6518ed5a..a5cdcc10b5 100644 --- a/man3/aio_init.3 +++ b/man3/aio_init.3 @@ -42,7 +42,7 @@ function allows the caller to provide tuning hints to the glibc POSIX AIO implementation. Use of this function is optional, but to be effective, it must be called before employing any other functions in the POSIX AIO API. - +.PP The tuning information is provided in the buffer pointed to by the argument .IR init . This buffer is a structure of the following form: diff --git a/man3/aio_read.3 b/man3/aio_read.3 index 1247262c11..bf6a02981d 100644 --- a/man3/aio_read.3 +++ b/man3/aio_read.3 @@ -38,9 +38,9 @@ function queues the I/O request described by the buffer pointed to by This function is the asynchronous analog of .BR read (2). The arguments of the call - +.PP read(fd, buf, count) - +.PP correspond (in order) to the fields .IR aio_fildes , .IR aio_buf , @@ -151,7 +151,7 @@ The buffer area being read into .\" or the control block of the operation must not be accessed during the operation or undefined results may occur. The memory areas involved must remain valid. - +.PP Simultaneous I/O operations specifying the same .I aiocb structure produce undefined results. diff --git a/man3/aio_return.3 b/man3/aio_return.3 index 07867f0074..e066aa38d0 100644 --- a/man3/aio_return.3 +++ b/man3/aio_return.3 @@ -56,7 +56,7 @@ or .BR fdatasync (2), call. On error, \-1 is returned, and \fIerrno\fP is set appropriately. - +.PP If the asynchronous I/O operation has not yet completed, the return value and effect of .BR aio_return () diff --git a/man3/aio_suspend.3 b/man3/aio_suspend.3 index 33985245b1..c0343abe9b 100644 --- a/man3/aio_suspend.3 +++ b/man3/aio_suspend.3 @@ -122,13 +122,13 @@ POSIX.1-2001, POSIX.1-2008. One can achieve polling by using a non-NULL .I timeout that specifies a zero time interval. - +.PP If one or more of the asynchronous I/O operations specified in .IR aiocb_list has already completed at the time of the call to .BR aio_suspend (), then the call returns immediately. - +.PP To determine which I/O operations have completed after a successful return from .BR aio_suspend (), diff --git a/man3/aio_write.3 b/man3/aio_write.3 index dbdbcd9aa9..8bac39c49c 100644 --- a/man3/aio_write.3 +++ b/man3/aio_write.3 @@ -38,9 +38,9 @@ function queues the I/O request described by the buffer pointed to by This function is the asynchronous analog of .BR write (2). The arguments of the call - +.PP write(fd, buf, count) - +.PP correspond (in order) to the fields .IR aio_fildes , .IR aio_buf , @@ -156,7 +156,7 @@ The buffer area being written out .\" or the control block of the operation must not be accessed during the operation or undefined results may occur. The memory areas involved must remain valid. - +.PP Simultaneous I/O operations specifying the same .I aiocb structure produce undefined results. diff --git a/man3/alloca.3 b/man3/alloca.3 index f5087ceafb..1b68f6ea2e 100644 --- a/man3/alloca.3 +++ b/man3/alloca.3 @@ -76,7 +76,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO This function is not in POSIX.1. - +.PP There is evidence that the .BR alloca () function appeared in 32V, PWB, PWB.2, 3BSD, and 4BSD. @@ -97,7 +97,7 @@ it can also simplify memory deallocation in applications that use or .BR siglongjmp (3). Otherwise, its use is discouraged. - +.PP Because the space allocated by .BR alloca () is allocated within the stack frame, @@ -106,7 +106,7 @@ is jumped over by a call to .BR longjmp (3) or .BR siglongjmp (3). - +.PP Do not attempt to .BR free (3) space allocated by @@ -154,7 +154,7 @@ There is no error indication if the stack frame cannot be extended. (However, after a failed allocation, the program is likely to receive a .B SIGSEGV signal if it attempts to access the unallocated space.) - +.PP On many systems .BR alloca () cannot be used inside the list of arguments of a function call, because diff --git a/man3/argz_add.3 b/man3/argz_add.3 index a164221b0a..62a0cc7084 100644 --- a/man3/argz_add.3 +++ b/man3/argz_add.3 @@ -223,7 +223,7 @@ T{ .BR argz_stringify () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are a GNU extension. Handle with care. diff --git a/man3/asin.3 b/man3/asin.3 index 099eb208cf..c8dd8d3eff 100644 --- a/man3/asin.3 +++ b/man3/asin.3 @@ -71,16 +71,16 @@ that is the value whose sine is On success, these functions return the principal value of the arc sine of .IR x in radians; the return value is in the range [\-pi/2,\ pi/2]. - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is outside the range [\-1,\ 1], @@ -120,7 +120,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/asinh.3 b/man3/asinh.3 index 601ca953bc..9d75206129 100644 --- a/man3/asinh.3 +++ b/man3/asinh.3 @@ -79,15 +79,15 @@ that is the value whose hyperbolic sine is .SH RETURN VALUE On success, these functions return the inverse hyperbolic sine of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is positive infinity (negative infinity), @@ -113,7 +113,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/asprintf.3 b/man3/asprintf.3 index b89a98ed9e..93cf08b0ad 100644 --- a/man3/asprintf.3 +++ b/man3/asprintf.3 @@ -71,7 +71,7 @@ T{ .BR vasprintf () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO These functions are GNU extensions, not in C or POSIX. They are also available under *BSD. diff --git a/man3/assert.3 b/man3/assert.3 index f3b4015c06..03d4e2f9f4 100644 --- a/man3/assert.3 +++ b/man3/assert.3 @@ -38,7 +38,7 @@ assert \- abort the program if assertion is false This macro can help programmers find bugs in their programs, or handle exceptional cases via a crash that will produce limited debugging output. - +.PP If .I expression is false (i.e., compares equal to zero), @@ -50,9 +50,9 @@ The error message includes the name of the file and function containing the .BR assert () call, the source code line number of the call, and the text of the argument; something like: - +.PP prog: some_file.c:16: some_func: Assertion `val == 0' failed. - +.PP If the macro .B NDEBUG is defined at the moment @@ -80,7 +80,7 @@ T{ .BR assert () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99. In C89, diff --git a/man3/assert_perror.3 b/man3/assert_perror.3 index 3a362e0466..2192f70ec1 100644 --- a/man3/assert_perror.3 +++ b/man3/assert_perror.3 @@ -68,7 +68,7 @@ T{ .BR assert_perror () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO This is a GNU extension. .SH BUGS diff --git a/man3/atan.3 b/man3/atan.3 index 989ea9fe77..f5761677d3 100644 --- a/man3/atan.3 +++ b/man3/atan.3 @@ -71,16 +71,16 @@ that is the value whose tangent is On success, these functions return the principal value of the arc tangent of .IR x in radians; the return value is in the range [\-pi/2,\ pi/2]. - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is positive infinity (negative infinity), +pi/2 (\-pi/2) is returned. @@ -105,7 +105,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/atan2.3 b/man3/atan2.3 index ebda957896..3c1e84e208 100644 --- a/man3/atan2.3 +++ b/man3/atan2.3 @@ -69,31 +69,31 @@ the quadrant of the result. On success, these functions return the principal value of the arc tangent of .IR y/x in radians; the return value is in the range [\-pi,\ pi]. - +.PP If .I y is +0 (\-0) and .I x is less than 0, +pi (\-pi) is returned. - +.PP If .I y is +0 (\-0) and .I x is greater than 0, +0 (\-0) is returned. - +.PP If .I y is less than 0 and .I x is +0 or \-0, \-pi/2 is returned. - +.PP If .I y is greater than 0 and .I x is +0 or \-0, pi/2 is returned. - +.PP .\" POSIX.1 says: .\" If .\" .I x @@ -104,7 +104,7 @@ If either or .I y is NaN, a NaN is returned. - +.PP .\" POSIX.1 says: .\" If the result underflows, a range error may occur and .\" .I y/x @@ -115,38 +115,38 @@ If is +0 (\-0) and .I x is \-0, +pi (\-pi) is returned. - +.PP If .I y is +0 (\-0) and .I x is +0, +0 (\-0) is returned. - +.PP If .I y is a finite value greater (less) than 0, and .I x is negative infinity, +pi (\-pi) is returned. - +.PP If .I y is a finite value greater (less) than 0, and .I x is positive infinity, +0 (\-0) is returned. - +.PP If .I y is positive infinity (negative infinity), and .I x is finite, pi/2 (\-pi/2) is returned. - +.PP If .I y is positive infinity (negative infinity) and .I x is negative infinity, +3*pi/4 (\-3*pi/4) is returned. - +.PP If .I y is positive infinity (negative infinity) and @@ -175,7 +175,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/atanh.3 b/man3/atanh.3 index 92085f5b2f..5341fd5cae 100644 --- a/man3/atanh.3 +++ b/man3/atanh.3 @@ -79,15 +79,15 @@ that is the value whose hyperbolic tangent is .SH RETURN VALUE On success, these functions return the inverse hyperbolic tangent of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is +1 or \-1, @@ -98,7 +98,7 @@ and the functions return or .BR HUGE_VALL , respectively, with the mathematically correct sign. - +.PP If the absolute value of .I x is greater than 1, @@ -147,7 +147,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/atexit.3 b/man3/atexit.3 index 044d8a952e..6c1176f92e 100644 --- a/man3/atexit.3 +++ b/man3/atexit.3 @@ -51,7 +51,7 @@ or via return from the program's .IR main (). Functions so registered are called in the reverse order of their registration; no arguments are passed. - +.PP The same function may be registered multiple times: it is called once for each registration. .LP @@ -86,7 +86,7 @@ T{ .BR atexit () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. .SH NOTES @@ -96,14 +96,14 @@ Functions registered using .BR on_exit (3)) are not called if a process terminates abnormally because of the delivery of a signal. - +.PP If one of the functions registered functions calls .BR _exit (2), then any remaining functions are not invoked, and the other process termination steps performed by .BR exit (3) are not performed. - +.PP POSIX.1 says that the result of calling .\" POSIX.1-2001, POSIX.1-2008 .BR exit (3) @@ -121,7 +121,7 @@ portable programs should not invoke .BR exit (3) inside a function registered using .BR atexit (). - +.PP The .BR atexit () and @@ -130,7 +130,7 @@ functions register functions on the same list: at normal process termination, the registered functions are invoked in reverse order of their registration by these two functions. - +.PP According to POSIX.1, the result is undefined if .BR longjmp (3) is used to terminate execution of one of the functions registered diff --git a/man3/backtrace.3 b/man3/backtrace.3 index 7cc8764aca..064d439fa2 100644 --- a/man3/backtrace.3 +++ b/man3/backtrace.3 @@ -75,7 +75,7 @@ to obtain the complete backtrace, make sure that and .I size are large enough. - +.PP Given the set of addresses returned by .BR backtrace () in @@ -100,7 +100,7 @@ by and must be freed by the caller. (The strings pointed to by the array of pointers need not and should not be freed.) - +.PP .BR backtrace_symbols_fd () takes the same .I buffer @@ -127,7 +127,7 @@ then the full backtrace was stored; if it is equal to .IR size , then it may have been truncated, in which case the addresses of the oldest stack frames are not returned. - +.PP On success, .BR backtrace_symbols () returns a pointer to the array diff --git a/man3/basename.3 b/man3/basename.3 index a90d420a5f..a8e078ab59 100644 --- a/man3/basename.3 +++ b/man3/basename.3 @@ -173,7 +173,7 @@ the POSIX versions of these functions modify the .I path argument, and segfault when called with a static string such as "/usr/". - +.PP Before glibc 2.2.1, the glibc version of .BR dirname () did not correctly handle pathnames with trailing \(aq/\(aq characters, diff --git a/man3/bindresvport.3 b/man3/bindresvport.3 index 023520b2ed..ef920fc71c 100644 --- a/man3/bindresvport.3 +++ b/man3/bindresvport.3 @@ -46,7 +46,7 @@ file descriptor to a privileged anonymous IP port, that is, a port number arbitrarily selected from the range 512 to 1023. .\" Glibc actually starts searching with a port # in the range 600 to 1023 - +.PP If the .BR bind (2) performed by @@ -56,7 +56,7 @@ is successful, and is not NULL, then .I sin\->sin_port returns the port number actually allocated. - +.PP .I sin can be NULL, in which case .I sin\->sin_family diff --git a/man3/bsd_signal.3 b/man3/bsd_signal.3 index 30004632f2..3aaf60d1a5 100644 --- a/man3/bsd_signal.3 +++ b/man3/bsd_signal.3 @@ -54,7 +54,7 @@ The .BR bsd_signal () function takes the same arguments, and performs the same task, as .BR signal (2). - +.PP The difference between the two is that .BR bsd_signal () is guaranteed to provide reliable signal semantics, that is: @@ -101,7 +101,7 @@ Use of should be avoided; use .BR sigaction (2) instead. - +.PP On modern Linux systems, .BR bsd_signal () and @@ -112,7 +112,7 @@ But on older systems, provided unreliable signal semantics; see .BR signal (2) for details. - +.PP The use of .I sighandler_t is a GNU extension; diff --git a/man3/bsearch.3 b/man3/bsearch.3 index 1124e421b5..d93b10aa94 100644 --- a/man3/bsearch.3 +++ b/man3/bsearch.3 @@ -86,7 +86,7 @@ T{ .BR bsearch () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. .SH EXAMPLE diff --git a/man3/bswap.3 b/man3/bswap.3 index 5d75295c04..b1aa6e66b2 100644 --- a/man3/bswap.3 +++ b/man3/bswap.3 @@ -46,7 +46,7 @@ These macros are GNU extensions. The program below swaps the bytes of the 8-byte integer supplied as its command-line argument. The following shell session demonstrates the use of the program: - +.PP .nf .in +4n $ \fB./a.out 0x0123456789abcdef\fP diff --git a/man3/btree.3 b/man3/btree.3 index bd3f32c691..6f3487a5b9 100644 --- a/man3/btree.3 +++ b/man3/btree.3 @@ -51,7 +51,7 @@ Since version 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. - +.PP The routine .BR dbopen (3) is the library interface to database files. @@ -242,13 +242,13 @@ Only big and little endian byte order is supported. .BR hash (3), .BR mpool (3), .BR recno (3) - +.PP .IR "The Ubiquitous B-tree" , Douglas Comer, ACM Comput. Surv. 11, 2 (June 1979), 121-138. - +.PP .IR "Prefix B-trees" , Bayer and Unterauer, ACM Transactions on Database Systems, Vol. 2, 1 (March 1977), 11-26. - +.PP .IR "The Art of Computer Programming Vol. 3: Sorting and Searching" , D.E. Knuth, 1968, pp 471-480. diff --git a/man3/byteorder.3 b/man3/byteorder.3 index f438e4e7e1..a30b6c4d05 100644 --- a/man3/byteorder.3 +++ b/man3/byteorder.3 @@ -90,7 +90,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. - +.PP Some systems require the inclusion of .I <netinet/in.h> instead of diff --git a/man3/bzero.3 b/man3/bzero.3 index b176b36516..634ec8638b 100644 --- a/man3/bzero.3 +++ b/man3/bzero.3 @@ -43,7 +43,7 @@ function erases the data in the bytes of the memory starting at the location pointed to by .IR s , by writing zeroes (bytes containing \(aq\\0\(aq) to that area. - +.PP The .BR explicit_bzero () function performs the same task as @@ -82,7 +82,7 @@ POSIX.1-2008 removes the specification of The .BR bzero () function first appeared in 4.3BSD. - +.PP The .BR explicit_bzero () function is a nonstandard extension that is also present on some of the BSDs. @@ -110,7 +110,7 @@ by an incorrect or compromised program. Calls to .BR explicit_bzero () are never optimized away by the compiler. - +.PP The .BR explicit_bzero () function does not solve all problems associated with erasing sensitive data: @@ -159,7 +159,7 @@ Indeed, it will make them worse, since, for example, it may force a variable that would otherwise have been optimized into a register to instead be maintained in (more vulnerable) RAM for its entire lifetime. - +.PP Notwithstanding the above details, for security-conscious applications, using .BR explicit_bzero () is generally preferable to not using it. diff --git a/man3/canonicalize_file_name.3 b/man3/canonicalize_file_name.3 index 1d190a1183..3d40eb981c 100644 --- a/man3/canonicalize_file_name.3 +++ b/man3/canonicalize_file_name.3 @@ -46,17 +46,17 @@ pathname components. Consecutive slash .RI ( / ) characters are replaced by a single slash. - +.PP The returned string is dynamically allocated by .BR canonicalize_file_name () and the caller should deallocate it with .BR free (3) when it is no longer required. - +.PP The call .I canonicalize_file_name(path) is equivalent to the call: - +.PP realpath(path, NULL); .SH RETURN VALUE On success, diff --git a/man3/carg.3 b/man3/carg.3 index bab08dcf3b..3bcf22688b 100644 --- a/man3/carg.3 +++ b/man3/carg.3 @@ -21,14 +21,14 @@ Link with \fI\-lm\fP. These functions calculate the complex argument (also called phase angle) of .IR z , with a branch cut along the negative real axis. - +.PP A complex number can be described by two real coordinates. One may use rectangular coordinates and gets - +.PP .nf z = x + I * y .fi - +.PP where .IR "x\ =\ creal(z)" and diff --git a/man3/cbrt.3 b/man3/cbrt.3 index 6fbc1461bf..9b22a3cc55 100644 --- a/man3/cbrt.3 +++ b/man3/cbrt.3 @@ -74,7 +74,7 @@ representable real cube root. .SH RETURN VALUE These functions return the cube root of .IR x . - +.PP If .I x is +0, \-0, positive infinity, negative infinity, or NaN, diff --git a/man3/ccos.3 b/man3/ccos.3 index 031f93aff7..127911278a 100644 --- a/man3/ccos.3 +++ b/man3/ccos.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions calculate the complex cosine of .IR z . - +.PP The complex cosine function is defined as: .nf @@ -42,7 +42,7 @@ T{ .BR ccosl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/ccosh.3 b/man3/ccosh.3 index 6360832ed6..ff2c2b2c6f 100644 --- a/man3/ccosh.3 +++ b/man3/ccosh.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions calculate the complex hyperbolic cosine of .IR z . - +.PP The complex hyperbolic cosine function is defined as: .nf diff --git a/man3/ceil.3 b/man3/ceil.3 index c4f6c74d76..3ffe22943d 100644 --- a/man3/ceil.3 +++ b/man3/ceil.3 @@ -58,7 +58,7 @@ _ISOC99_SOURCE || _POSIX_C_SOURCE\ >=\ 200112L .SH DESCRIPTION These functions return the smallest integral value that is not less than .IR x . - +.PP For example, .IR ceil(0.5) is 1.0, and @@ -67,7 +67,7 @@ is 0.0. .SH RETURN VALUE These functions return the ceiling of .IR x . - +.PP If .I x is integral, +0, \-0, NaN, or infinite, @@ -92,7 +92,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to @@ -113,7 +113,7 @@ of the exponent is smaller than the number of mantissa bits. For the IEEE-754 standard 32-bit and 64-bit floating-point numbers the maximum value of the exponent is 128 (respectively, 1024), and the number of mantissa bits is 24 (respectively, 53).) - +.PP The integral value returned by these functions may be too large to store in an integer type .RI ( int , diff --git a/man3/cexp.3 b/man3/cexp.3 index f717849d05..4c535a2e32 100644 --- a/man3/cexp.3 +++ b/man3/cexp.3 @@ -43,7 +43,7 @@ T{ .BR cexpl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/clearenv.3 b/man3/clearenv.3 index a7a3a372ea..7dc311fe7f 100644 --- a/man3/clearenv.3 +++ b/man3/clearenv.3 @@ -73,7 +73,7 @@ T{ .BR clearenv () T} Thread safety MT-Unsafe const:env .TE - +.sp 1 .SH CONFORMING TO Various UNIX variants (DG/UX, HP-UX, QNX, ...). POSIX.9 (bindings for FORTRAN77). @@ -98,7 +98,7 @@ is unavailable, the assignment .fi will probably do. - +.PP The .BR clearenv () function may be useful in security-conscious applications that want to @@ -107,14 +107,14 @@ executed using .BR exec (3). The application would do this by first clearing the environment and then adding select environment variables. - +.PP Note that the main effect of .BR clearenv () is to adjust the value of the pointer .BR environ (7); this function does not erase the contents of the buffers containing the environment definitions. - +.PP The DG/UX and Tru64 man pages write: If .I environ has been modified by anything other than the diff --git a/man3/clock.3 b/man3/clock.3 index be4dd72e19..f8779f4155 100644 --- a/man3/clock.3 +++ b/man3/clock.3 @@ -59,7 +59,7 @@ T{ .BR clock () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99. XSI requires that @@ -96,7 +96,7 @@ The .BR times (2) function, which explicitly returns (separate) information about the caller and its children, may be preferable. - +.PP In glibc 2.17 and earlier, .BR clock () was implemented on top of diff --git a/man3/clog.3 b/man3/clog.3 index 812cf0f711..7904f27f06 100644 --- a/man3/clog.3 +++ b/man3/clog.3 @@ -21,7 +21,7 @@ Link with \fI\-lm\fP. These functions calculate the complex natural logarithm of .IR z , with a branch cut along the negative real axis. - +.PP The logarithm .BR clog () is the inverse function of the exponential diff --git a/man3/clog10.3 b/man3/clog10.3 index 299a7a051c..1c863609da 100644 --- a/man3/clog10.3 +++ b/man3/clog10.3 @@ -23,18 +23,18 @@ Link with \fI\-lm\fP. The call .I clog10(z) is equivalent to: - +.PP clog(z)/log(10) - +.PP or equally: - +.PP log10(cabs(c)) + I * carg(c) / log(10) - +.PP The other functions perform the same task for .I float and .IR "long double" . - +.PP Note that .I z close to zero will cause an overflow. diff --git a/man3/clog2.3 b/man3/clog2.3 index 63f72946b9..7c4d73d06d 100644 --- a/man3/clog2.3 +++ b/man3/clog2.3 @@ -22,12 +22,12 @@ The call .I clog2(z) is equivalent to .IR clog(z)/log(2) . - +.PP The other functions perform the same task for .I float and .IR "long double" . - +.PP Note that .I z close to zero will cause an overflow. diff --git a/man3/confstr.3 b/man3/confstr.3 index 861f34f3ca..9178e59b50 100644 --- a/man3/confstr.3 +++ b/man3/confstr.3 @@ -105,7 +105,7 @@ This value may be greater than which means that the value in .I buf is truncated. - +.PP If .I name is a valid configuration variable, diff --git a/man3/copysign.3 b/man3/copysign.3 index ea535297b0..e9374c3af3 100644 --- a/man3/copysign.3 +++ b/man3/copysign.3 @@ -64,7 +64,7 @@ These functions return a value whose absolute value matches that of .IR x , but whose sign bit matches that of .IR y . - +.PP For example, .I "copysign(42.0,\ \-1.0)" and @@ -75,7 +75,7 @@ On success, these functions return a value whose magnitude is taken from .I x and whose sign is taken from .IR y . - +.PP If .I x is a NaN, diff --git a/man3/cos.3 b/man3/cos.3 index c33bbc4976..dda4eb2ebf 100644 --- a/man3/cos.3 +++ b/man3/cos.3 @@ -71,11 +71,11 @@ given in radians. .SH RETURN VALUE On success, these functions return the cosine of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity or negative infinity, @@ -113,7 +113,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/cosh.3 b/man3/cosh.3 index 32dd5f79b6..56df0628d2 100644 --- a/man3/cosh.3 +++ b/man3/cosh.3 @@ -74,20 +74,20 @@ which is defined mathematically as: .SH RETURN VALUE On success, these functions return the hyperbolic cosine of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 or \-0, 1 is returned. - +.PP If .I x is positive infinity or negative infinity, positive infinity is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -127,7 +127,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/crypt.3 b/man3/crypt.3 index 35185c43f5..032e460651 100644 --- a/man3/crypt.3 +++ b/man3/crypt.3 @@ -105,7 +105,7 @@ If you are planning on using the .BR crypt () interface for a cryptography project, don't do it: get a good book on encryption and one of the widely available DES libraries. - +.PP .BR crypt_r () is a reentrant version of .BR crypt (). @@ -193,15 +193,15 @@ is a GNU extension. .SS Glibc notes The glibc2 version of this function supports additional encryption algorithms. - +.PP If .I salt is a character string starting with the characters "$\fIid\fP$" followed by a string terminated by "$": .RS - +.PP $\fIid\fP$\fIsalt\fP$\fIencrypted\fP - +.PP .RE then instead of using the DES machine, .I id @@ -228,11 +228,11 @@ _ 6 | SHA-512 (since glibc 2.7) .TE .RE - +.PP So $5$\fIsalt\fP$\fIencrypted\fP is an SHA-256 encoded password and $6$\fIsalt\fP$\fIencrypted\fP is an SHA-512 encoded one. - +.PP "\fIsalt\fP" stands for the up to 16 characters following "$\fIid\fP$" in the salt. The encrypted part of the password string is the actual computed password. @@ -243,7 +243,7 @@ MD5 | 22 characters SHA-256 | 43 characters SHA-512 | 86 characters .TE - +.sp 1 The characters in "\fIsalt\fP" and "\fIencrypted\fP" are drawn from the set [\fBa\-zA\-Z0\-9./\fP]. In the MD5 and SHA implementations the entire diff --git a/man3/csin.3 b/man3/csin.3 index 2a74c461c0..bc29ced2ef 100644 --- a/man3/csin.3 +++ b/man3/csin.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions calculate the complex sine of .IR z . - +.PP The complex sine function is defined as: .nf @@ -42,7 +42,7 @@ T{ .BR csinl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/csinh.3 b/man3/csinh.3 index 7dfeda96ce..1cde4522a9 100644 --- a/man3/csinh.3 +++ b/man3/csinh.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions calculate the complex hyperbolic sine of .IR z . - +.PP The complex hyperbolic sine function is defined as: .nf @@ -42,7 +42,7 @@ T{ .BR csinhl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/csqrt.3 b/man3/csqrt.3 index 3f7b0080bd..d5b0baa45a 100644 --- a/man3/csqrt.3 +++ b/man3/csqrt.3 @@ -40,7 +40,7 @@ T{ .BR csqrtl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/ctan.3 b/man3/ctan.3 index 8c9b3cb75a..c718b85e49 100644 --- a/man3/ctan.3 +++ b/man3/ctan.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions calculate the complex tangent of .IR z . - +.PP The complex tangent function is defined as: .nf @@ -42,7 +42,7 @@ T{ .BR ctanl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/ctanh.3 b/man3/ctanh.3 index 9f3c2edd76..31cda778ed 100644 --- a/man3/ctanh.3 +++ b/man3/ctanh.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions calculate the complex hyperbolic tangent of .IR z . - +.PP The complex hyperbolic tangent function is defined mathematically as: .nf @@ -43,7 +43,7 @@ T{ .BR ctanhl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/ctime.3 b/man3/ctime.3 index f39ef0b0b3..4d0794017d 100644 --- a/man3/ctime.3 +++ b/man3/ctime.3 @@ -246,7 +246,7 @@ and a negative value means that .BR mktime () should (use timezone information and system databases to) attempt to determine whether DST is in effect at the specified time. - +.PP The .BR mktime () function modifies the fields of the @@ -266,7 +266,7 @@ Calling .BR mktime () also sets the external variable \fItzname\fP with information about the current timezone. - +.PP If the specified broken-down time cannot be represented as calendar time (seconds since the Epoch), .BR mktime () @@ -281,33 +281,33 @@ and .BR localtime () return a pointer to a .IR "struct\ tm" . - +.PP On success, .BR gmtime_r () and .BR localtime_r () return the address of the structure pointed to by .IR result . - +.PP On success, .BR asctime () and .BR ctime () return a pointer to a string. - +.PP On success, .BR asctime_r () and .BR ctime_r () return a pointer to the string pointed to by .IR buf . - +.PP On success, .BR mktime () returns the calendar time (seconds since the Epoch), expressed as a value of type .IR time_t . - +.PP On error, .BR mktime () returns the value @@ -388,7 +388,7 @@ The thread-safe versions, and .BR localtime_r (), are specified by SUSv2. - +.PP POSIX.1-2001 says: "The .BR asctime (), @@ -421,7 +421,7 @@ defined when was set before including .IR <time.h> . This is a BSD extension, present in 4.3BSD-Reno. - +.PP According to POSIX.1-2004, .BR localtime () is required to behave as though diff --git a/man3/dbopen.3 b/man3/dbopen.3 index 1ff08e5d60..3ff075b9e4 100644 --- a/man3/dbopen.3 +++ b/man3/dbopen.3 @@ -55,7 +55,7 @@ Since version 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. - +.PP .BR dbopen () is the library interface to database files. The supported file formats are btree, hashed and UNIX file oriented. @@ -556,6 +556,6 @@ locking, or transactions. .BR hash (3), .BR mpool (3), .BR recno (3) - +.PP .IR "LIBTP: Portable, Modular Transactions for UNIX" , Margo Seltzer, Michael Olson, USENIX proceedings, Winter 1992. diff --git a/man3/dl_iterate_phdr.3 b/man3/dl_iterate_phdr.3 index 7c49ffa5f0..a464f4355d 100644 --- a/man3/dl_iterate_phdr.3 +++ b/man3/dl_iterate_phdr.3 @@ -41,7 +41,7 @@ The function allows an application to inquire at run time to find out which shared objects it has loaded, and the order in which they were loaded. - +.PP The .BR dl_iterate_phdr () function walks through the list of an @@ -51,7 +51,7 @@ once for each object, until either all shared objects have been processed or .I callback returns a nonzero value. - +.PP Each call to .I callback receives three arguments: @@ -68,11 +68,11 @@ program as the second argument (also named .IR data ) in the call to .BR dl_iterate_phdr (). - +.PP The .I info argument is a structure of the following type: - +.PP .in +4n .nf struct dl_phdr_info { @@ -106,7 +106,7 @@ struct dl_phdr_info { }; .fi .in - +.PP (The .IR ElfW () macro definition turns its argument into the name of an ELF data @@ -118,7 +118,7 @@ yields the data type name Further information on these types can be found in the .IR <elf.h> " and " <link.h> header files.) - +.PP The .I dlpi_addr field indicates the base address of the shared object @@ -129,7 +129,7 @@ The .I dlpi_name field is a null-terminated string giving the pathname from which the shared object was loaded. - +.PP To understand the meaning of the .I dlpi_phdr and @@ -144,7 +144,7 @@ shared object. The .I dlpi_phnum field indicates the size of this array. - +.PP These program headers are structures of the following form: .in +4n .nf @@ -161,21 +161,21 @@ typedef struct { } Elf32_Phdr; .fi .in - +.PP Note that we can calculate the location of a particular program header, .IR x , in virtual memory using the formula: - +.PP .nf addr == info\->dlpi_addr + info\->dlpi_phdr[x].p_vaddr; .fi - +.PP Possible values for .I p_type include the following (see .IR <elf.h> for further details): - +.PP .nf .in +4n #define PT_LOAD 1 /* Loadable program segment */ @@ -211,7 +211,7 @@ T{ .BR dl_iterate_phdr () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO The .BR dl_iterate_phdr () @@ -234,7 +234,7 @@ structure; in that event, the .I size argument provides a mechanism for the callback function to discover whether it is running on a system with added fields. - +.PP The first object visited by .IR callback is the main program. @@ -247,7 +247,7 @@ shared objects it has loaded. For each shared object, the program lists some information (virtual address, size, flags, and type) for each of the objects ELF segments. - +.PP The following shell session demonstrates the output produced by the program on an x86-64 system. The first shared object for which output is displayed @@ -292,7 +292,7 @@ Name: "/lib64/ld-linux-x86-64.so.2" (7 segments) 6: [0x7f55718afba0; memsz: 460] flags: 0x4; PT_GNU_RELRO .in .fi - +.PP .SS Program source \& .nf @@ -352,6 +352,6 @@ main(int argc, char *argv[]) .BR dlopen (3), .BR elf (5), .BR ld.so (8) - +.PP .IR "Executable and Linking Format Specification" , available at various locations online. diff --git a/man3/dladdr.3 b/man3/dladdr.3 index 237fb64c14..971cb10976 100644 --- a/man3/dladdr.3 +++ b/man3/dladdr.3 @@ -75,7 +75,7 @@ could be found, then and .I dli_saddr are set to NULL. - +.PP The function .BR dladdr1 () is like @@ -97,7 +97,7 @@ structure (i.e., defined in .I <link.h> as: - +.IP .in +4n .nf struct link_map { @@ -134,7 +134,7 @@ yields the data type name which is defined in .IR <elf.h> as: - +.IP .in +4n .nf typedef struct { @@ -147,11 +147,11 @@ typedef struct { } Elf64_Sym; .fi .in - +.IP The .I st_name field is an index into the string table. - +.IP The .I st_info field encodes the symbol's type and binding. @@ -223,7 +223,7 @@ but not to a symbol in the shared object, then the and .I info->dli_saddr fields are set to NULL. - +.PP If the address specified in .I addr could not be matched to a shared object, then these functions return 0. diff --git a/man3/dlerror.3 b/man3/dlerror.3 index d517cfe1f8..a1f311c4a9 100644 --- a/man3/dlerror.3 +++ b/man3/dlerror.3 @@ -42,7 +42,7 @@ since the last call to The returned string does .I not include a trailing newline. - +.PP .BR dlerror () returns NULL if no errors have occurred since initialization or since it was last called. diff --git a/man3/dlinfo.3 b/man3/dlinfo.3 index 8de25ab2a4..3a065ffed2 100644 --- a/man3/dlinfo.3 +++ b/man3/dlinfo.3 @@ -54,7 +54,7 @@ The argument is a pointer to a buffer used to store information returned by the call; the type of this argument depends on .IR request . - +.PP The following values are supported for .IR request (with the corresponding type for @@ -78,7 +78,7 @@ argument points to a pointer to a structure, defined in .I <link.h> as: - +.IP .in +4n .nf struct link_map { @@ -154,7 +154,7 @@ to obtain the library search paths. The .I Dl_serinfo structure is defined as follows: - +.IP .in +4n .nf typedef struct { @@ -171,7 +171,7 @@ typedef struct { Each of the .I dls_serpath elements in the above structure is a structure of the following form: - +.IP .in +4n .nf typedef struct { @@ -182,7 +182,7 @@ typedef struct { } Dl_serpath; .fi .in - +.IP The .I dls_flags field is currently unused, and always contains zero. @@ -250,7 +250,7 @@ and .B RTLD_DI_SERINFO requests to obtain the library search path list for the library. Here is an example of what we might see when running the program: - +.PP .in +4n .nf $ \fB./a.out /lib64/libm.so.6\fP diff --git a/man3/dlopen.3 b/man3/dlopen.3 index 1df770b5db..f69fadf1a9 100644 --- a/man3/dlopen.3 +++ b/man3/dlopen.3 @@ -65,7 +65,7 @@ This handle is employed with other functions in the dlopen API, such as .BR dlinfo (3), and .BR dlclose (). - +.PP If .I filename .\" FIXME On Solaris, when handle is NULL, we seem to get back @@ -242,7 +242,7 @@ and .I flags arguments, as well as the return value, are the same, except for the differences noted below. - +.PP The .BR dlmopen () function differs from @@ -261,7 +261,7 @@ call is made.) The .I Lmid_t type is an opaque handle that refers to a namespace. - +.PP The .I lmid argument is either the ID of an existing namespace @@ -300,7 +300,7 @@ All shared objects that were automatically loaded when was invoked on the object referred to by .I handle are recursively closed in the same manner. - +.PP A successful return from .BR dlclose () does not guarantee that the symbols associated with @@ -322,11 +322,11 @@ On error (file could not be found, was not readable, had the wrong format, or caused errors during loading), these functions return NULL. - +.PP On success, .BR dlclose () returns 0; on error, it returns a nonzero value. - +.PP Errors from these functions can be diagnosed using .BR dlerror (3). .SH VERSIONS @@ -358,7 +358,7 @@ and The .BR dlmopen () function is a GNU extension. - +.PP The .BR RTLD_NOLOAD , .BR RTLD_NODELETE , @@ -375,7 +375,7 @@ dependent shared objects are implicitly loaded according to the usual rules, and symbol references are likewise resolved according to the usual rules, but such resolution is confined to the definitions provided by the objects that have been (explicitly and implicitly) loaded into the namespace. - +.PP The .BR dlmopen () function permits object-load isolation\(emthe ability @@ -395,7 +395,7 @@ without exposing those symbols to the entire application. This can be achieved by using a separate namespace and the .B RTLD_GLOBAL flag. - +.PP The .BR dlmopen () function also can be used to provide better isolation than the @@ -411,7 +411,7 @@ Thus, .BR RTLD_LOCAL is insufficient to isolate a loaded shared object except in the (uncommon) case where one has explicit control over all shared object dependencies. - +.PP Possible uses of .BR dlmopen () are plugins where the author of the plugin-loading framework @@ -426,7 +426,7 @@ Using .BR dlmopen (), this can be achieved by loading the same shared object file into different namespaces. - +.PP The glibc implementation supports a maximum of .\" DL_NNS 16 namespaces. @@ -450,7 +450,7 @@ See the info pages (under "Function attributes") .\" info gcc "C Extensions" "Function attributes" for further information. - +.PP An older method of (partially) achieving the same result is via the use of two special symbols recognized by the linker: .B _init @@ -491,7 +491,7 @@ permit multiple initialization and finalization functions to be defined. .\" .\" void _init(void) __attribute__((constructor)); .\" .\" void _fini(void) __attribute__((destructor)); .\" - +.PP Since glibc 2.2.3, .BR atexit (3) can be used to register an exit handler that is automatically @@ -519,7 +519,7 @@ looks up the address of the .BR cos (3) function, and prints the cosine of 2.0. The following is an example of building and running the program: - +.PP .in +4n .nf $ \fBcc dlopen_demo.c \-ldl\fP @@ -594,5 +594,5 @@ main(void) .BR rtld-audit (7), .BR ld.so (8), .BR ldconfig (8) - +.PP gcc info pages, ld info pages diff --git a/man3/dlsym.3 b/man3/dlsym.3 index cd673f313a..4382e381c5 100644 --- a/man3/dlsym.3 +++ b/man3/dlsym.3 @@ -54,7 +54,7 @@ returns NULL. (The search performed by .BR dlsym () is breadth first through the dependency tree of these shared objects.) - +.PP Since the value of the symbol could actually be NULL (so that a NULL return from .BR dlsym () @@ -103,7 +103,7 @@ and .B RTLD_NEXT from .IR <dlfcn.h> . - +.PP .PP The function .BR dlvsym () diff --git a/man3/drand48_r.3 b/man3/drand48_r.3 index 0a4d3f9b95..aae2f14e4b 100644 --- a/man3/drand48_r.3 +++ b/man3/drand48_r.3 @@ -87,7 +87,7 @@ These functions are the reentrant analogs of the functions described in Instead of modifying the global random generator state, they use the supplied data .IR buffer . - +.PP Before the first use, this struct must be initialized, for example, by filling it with zeros, or by calling one of the functions .BR srand48_r (), diff --git a/man3/duplocale.3 b/man3/duplocale.3 index 5bc03d9c67..959a66f417 100644 --- a/man3/duplocale.3 +++ b/man3/duplocale.3 @@ -54,7 +54,7 @@ The .BR duplocale () function creates a duplicate of the locale object referred to by .IR locobj . - +.PP If .I locobj is @@ -95,7 +95,7 @@ other functions that employ a locale handle, such as This is done by applying .BR duplocale () to the value returned by the following call: - +.IP loc = uselocale((locale_t) 0); .IP This technique is necessary, because the above diff --git a/man3/encrypt.3 b/man3/encrypt.3 index ef3dee393d..c7a6a211f1 100644 --- a/man3/encrypt.3 +++ b/man3/encrypt.3 @@ -142,7 +142,7 @@ T} Thread safety MT-Safe .BR encrypt (), .BR setkey (): POSIX.1-2001, POSIX.1-2008, SUS, SVr4. - +.PP The functions .BR encrypt_r () and diff --git a/man3/end.3 b/man3/end.3 index 08f575b4eb..9f8f9d8310 100644 --- a/man3/end.3 +++ b/man3/end.3 @@ -53,7 +53,7 @@ they are not standardized; use with caution. .SH NOTES The program must explicitly declare these symbols; they are not defined in any header file. - +.PP On some systems the names of these symbols are preceded by underscores, thus: .IR _etext , @@ -61,7 +61,7 @@ thus: and .IR _end . These symbols are also defined for programs compiled on Linux. - +.PP At the start of program execution, the program break will be somewhere near .IR &end diff --git a/man3/endian.3 b/man3/endian.3 index 5e6a944d02..39f6ea851e 100644 --- a/man3/endian.3 +++ b/man3/endian.3 @@ -77,21 +77,21 @@ Feature Test Macro Requirements for glibc (see These functions convert the byte encoding of integer values from the byte order that the current CPU (the "host") uses, to and from little-endian and big-endian byte order. - +.PP The number, .IR nn , in the name of each function indicates the size of integer handled by the function, either 16, 32, or 64 bits. - +.PP The functions with names of the form "htobe\fInn\fP" convert from host byte order to big-endian order. - +.PP The functions with names of the form "htole\fInn\fP" convert from host byte order to little-endian order. - +.PP The functions with names of the form "be\fInn\fPtoh" convert from big-endian order to host byte order. - +.PP The functions with names of the form "le\fInn\fPtoh" convert from little-endian order to host byte order. .SH VERSIONS @@ -119,7 +119,7 @@ For example, .BR be32toh () is identical to .BR ntohl (). - +.PP The advantage of the .BR byteorder (3) functions is that they are standard functions available diff --git a/man3/envz_add.3 b/man3/envz_add.3 index dba21d9405..9d57ef518c 100644 --- a/man3/envz_add.3 +++ b/man3/envz_add.3 @@ -134,7 +134,7 @@ T{ .BR envz_strip () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are a GNU extension. Handle with care. diff --git a/man3/erf.3 b/man3/erf.3 index 544eb2a28a..28e947879e 100644 --- a/man3/erf.3 +++ b/man3/erf.3 @@ -77,20 +77,20 @@ defined as On success, these functions return the error function of .IR x , a value in the range [\-1,\ 1]. - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is positive infinity (negative infinity), +1 (\-1) is returned. - +.PP If .I x is subnormal, @@ -132,7 +132,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/erfc.3 b/man3/erfc.3 index 2d8558ffef..73319f4cab 100644 --- a/man3/erfc.3 +++ b/man3/erfc.3 @@ -66,28 +66,28 @@ that is, 1.0 \- erf(x). On success, these functions return the complementary error function of .IR x , a value in the range [0,2]. - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 or \-0, 1 is returned. - +.PP If .I x is positive infinity, +0 is returned. - +.PP If .I x is negative infinity, +2 is returned. - +.PP If the function result underflows and produces an unrepresentable value, the return value is 0.0. - +.PP If the function result underflows but produces a representable (i.e., subnormal) value, .\" e.g., erfc(27) on x86-32 @@ -129,7 +129,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/err.3 b/man3/err.3 index 1d38a69a7b..5c4ded1527 100644 --- a/man3/err.3 +++ b/man3/err.3 @@ -128,7 +128,7 @@ T{ .BR vwarnx () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO These functions are nonstandard BSD extensions. .\" .SH HISTORY diff --git a/man3/errno.3 b/man3/errno.3 index 046476bdb2..f6925cc9c3 100644 --- a/man3/errno.3 +++ b/man3/errno.3 @@ -50,12 +50,12 @@ a function that succeeds .I is allowed to change .IR errno . - +.PP Valid error numbers are all nonzero; .I errno is never set to zero by any system call or library function. - +.PP For some system calls and library functions (e.g., .BR getpriority (2)), \-1 is a valid return on success. @@ -67,7 +67,7 @@ if the call returns a status that indicates that an error may have occurred, checking to see if .I errno has a nonzero value. - +.PP .I errno is defined by the ISO C standard to be a modifiable lvalue of type @@ -78,14 +78,14 @@ may be a macro. .I errno is thread-local; setting it in one thread does not affect its value in any other thread. - +.PP All the error names specified by POSIX.1 must have distinct values, with the exception of .B EAGAIN and .BR EWOULDBLOCK , which may be the same. - +.PP .\" The following is now .\" POSIX.1 (2001 edition) lists the following symbolic error names. Of .\" these, \fBEDOM\fP and \fBERANGE\fP are in the ISO C standard. ISO C @@ -208,7 +208,7 @@ Identifier removed (POSIX.1). .TP .B EILSEQ Invalid or incomplete multibyte or wide character (POSIX.1, C99). - +.IP The text shown here is the glibc error description; in POSIX.1, this error is described as "Illegal byte sequence". .TP @@ -327,7 +327,7 @@ No such device (POSIX.1). .TP .B ENOENT No such file or directory (POSIX.1). - +.IP Typically, this error results when a specified pathname does not exist, or one of the components in the directory prefix of a pathname does not exist, or the specified pathname is a dangling symbolic link. diff --git a/man3/error.3 b/man3/error.3 index 660de39521..cbd165ab7b 100644 --- a/man3/error.3 +++ b/man3/error.3 @@ -61,7 +61,7 @@ should follow .I format in the argument list. The output is terminated by a newline character. - +.PP The program name printed by .BR error () is the value of the global variable @@ -72,13 +72,13 @@ initially has the same value as .IR argv[0] . The value of this variable can be modified to change the output of .BR error (). - +.PP If \fIstatus\fP has a nonzero value, then .BR error () calls .BR exit (3) to terminate the program using the given value as the exit status. - +.PP The .BR error_at_line () function is exactly the same as @@ -98,20 +98,20 @@ The preprocessor values \fB__LINE__\fP and .BR error_at_line (), but other values can also be used. For example, these arguments could refer to a location in an input file. - +.PP If the global variable \fIerror_one_per_line\fP is set nonzero, a sequence of .BR error_at_line () calls with the same value of \fIfilename\fP and \fIlinenum\fP will result in only one message (the first) being output. - +.PP The global variable \fIerror_message_count\fP counts the number of messages that have been output by .BR error () and .BR error_at_line (). - +.PP If the global variable \fIerror_print_progname\fP is assigned the address of a function (i.e., is not NULL), then that function is called @@ -137,7 +137,7 @@ MT-Unsafe\ race: error_at_line/error_one_per_line locale T} .TE .ad - +.PP The internal .I error_one_per_line variable is accessed (without any form of synchronization, but since it's an diff --git a/man3/euidaccess.3 b/man3/euidaccess.3 index ddbae47381..48323045e1 100644 --- a/man3/euidaccess.3 +++ b/man3/euidaccess.3 @@ -44,13 +44,13 @@ However, whereas performs checks using the real user and group identifiers of the process, .BR euidaccess () uses the effective identifiers. - +.PP .I mode is a mask consisting of one or more of .BR R_OK ", " W_OK ", " X_OK ", and " F_OK , with the same meanings as for .BR access (2). - +.PP .BR eaccess () is a synonym for .BR euidaccess (), @@ -96,7 +96,7 @@ performing some operation based on that information leads to race conditions: the file permissions may change between the two steps. Generally, it is safer just to attempt the desired operation and handle any permission error that occurs. - +.PP This function always dereferences symbolic links. If you need to check the permissions on a symbolic link, use .BR faccessat (2) diff --git a/man3/exec.3 b/man3/exec.3 index 9a061dd3ef..2a03fc59ff 100644 --- a/man3/exec.3 +++ b/man3/exec.3 @@ -158,13 +158,13 @@ the current directory followed by the list of directories returned by (This .BR confstr (3) call typically returns the value "/bin:/usr/bin".) - +.PP If the specified filename includes a slash character, then .B PATH is ignored, and the file at the specified pathname is executed. - +.PP In addition, certain errors are treated specially. - +.PP If permission is denied for a file (the attempted .BR execve (2) failed with the error @@ -175,7 +175,7 @@ they will return with .I errno set to .BR EACCES . - +.PP If the header of a file isn't recognized (the attempted .BR execve (2) failed with the error @@ -221,7 +221,7 @@ T} Thread safety MT-Safe env .TE .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. - +.PP The .BR execvpe () function is a GNU extension. diff --git a/man3/exp.3 b/man3/exp.3 index 65d4e76a0b..0a6b0c1ead 100644 --- a/man3/exp.3 +++ b/man3/exp.3 @@ -70,26 +70,26 @@ logarithms) raised to the power of .SH RETURN VALUE On success, these functions return the exponential value of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity, positive infinity is returned. - +.PP If .I x is negative infinity, +0 is returned. - +.PP If the result underflows, a range error occurs, and zero is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -103,7 +103,7 @@ See .BR math_error (7) for information on how to determine whether an error has occurred when calling these functions. - +.PP The following errors can occur: .TP Range error, overflow @@ -137,7 +137,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/exp10.3 b/man3/exp10.3 index 17c81bdcd3..77556e3674 100644 --- a/man3/exp10.3 +++ b/man3/exp10.3 @@ -56,7 +56,7 @@ raised to the power of .SH RETURN VALUE On success, these functions return the base-10 exponential value of .IR x . - +.PP For various special cases, including the handling of infinity and NaN, as well as overflows and underflows, see .BR exp (3). @@ -65,7 +65,7 @@ See .BR math_error (7) for information on how to determine whether an error has occurred when calling these functions. - +.PP For a discussion of the errors that can occur for these functions, see .BR exp (3). .SH VERSIONS diff --git a/man3/exp2.3 b/man3/exp2.3 index bc2e49d901..370e008c68 100644 --- a/man3/exp2.3 +++ b/man3/exp2.3 @@ -68,7 +68,7 @@ These functions return the value of 2 raised to the power of .SH RETURN VALUE On success, these functions return the base-2 exponential value of .IR x . - +.PP For various special cases, including the handling of infinity and NaN, as well as overflows and underflows, see .BR exp (3). @@ -77,7 +77,7 @@ See .BR math_error (7) for information on how to determine whether an error has occurred when calling these functions. - +.PP For a discussion of the errors that can occur for these functions, see .BR exp (3). .SH VERSIONS @@ -98,7 +98,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/expm1.3 b/man3/expm1.3 index a79ba420e0..9dd53c00c3 100644 --- a/man3/expm1.3 +++ b/man3/expm1.3 @@ -83,25 +83,25 @@ subtraction of two numbers that are nearly equal. .SH RETURN VALUE On success, these functions return .IR "exp(x)\ \-\ 1" . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is positive infinity, positive infinity is returned. - +.PP If .I x is negative infinity, \-1 is returned. - +.PP If the result overflows, a range error occurs, and the functions return .RB - HUGE_VAL , @@ -153,7 +153,7 @@ values (where the function result approaches \-1), raises a bogus underflow floating-point exception. .\" FIXME . .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6778 - +.PP For some large positive .I x values, @@ -164,7 +164,7 @@ overflow exception, and returns a NaN instead of positive infinity. .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6814 .\" e.g., expm1(1e5) through expm1(1.00199970127e5), .\" but not expm1(1.00199970128e5) and beyond. - +.PP Before version 2.11, .\" It looks like the fix was in 2.11, or possibly 2.12. .\" I have no test system for 2.11, but 2.12 passes. diff --git a/man3/fabs.3 b/man3/fabs.3 index a174c99b17..becf92417d 100644 --- a/man3/fabs.3 +++ b/man3/fabs.3 @@ -66,15 +66,15 @@ number .SH RETURN VALUE These functions return the absolute value of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is \-0, +0 is returned. - +.PP If .I x is negative infinity or positive infinity, positive infinity is returned. @@ -96,7 +96,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/fcloseall.3 b/man3/fcloseall.3 index 9b01d231ea..f21c56a2fd 100644 --- a/man3/fcloseall.3 +++ b/man3/fcloseall.3 @@ -40,7 +40,7 @@ Buffered output for each stream is written before it is closed (as for .BR fflush (3)); buffered input is discarded. - +.PP The standard streams, .IR stdin , .IR stdout , diff --git a/man3/fdim.3 b/man3/fdim.3 index 798d2b98b5..49479aced0 100644 --- a/man3/fdim.3 +++ b/man3/fdim.3 @@ -37,13 +37,13 @@ These functions return the positive difference, max(\fIx\fP-\fIy\fP,0), between their arguments. .SH RETURN VALUE On success, these functions return the positive difference. - +.PP If .I x or .I y is a NaN, a NaN is returned. - +.PP If the result overflows, a range error occurs, and the functions return diff --git a/man3/fenv.3 b/man3/fenv.3 index ba8f344c48..40c6c1bf43 100644 --- a/man3/fenv.3 +++ b/man3/fenv.3 @@ -160,7 +160,7 @@ round to nearest (the default), round up (toward positive infinity), round down (toward negative infinity), and round toward zero. - +.PP Each of the macros .BR FE_TONEAREST , .BR FE_UPWARD , @@ -179,7 +179,7 @@ The .BR fesetround () function sets the rounding mode as specified by its argument and returns zero when it was successful. - +.PP C99 and POSIX.1-2008 specify an identifier, .BR FLT_ROUNDS , defined in diff --git a/man3/ferror.3 b/man3/ferror.3 index b1892e150b..4d6d7e9839 100644 --- a/man3/ferror.3 +++ b/man3/ferror.3 @@ -126,7 +126,7 @@ The functions and .BR ferror () conform to C89, C99, POSIX.1-2001, and POSIX.1-2008. - +.PP The function .BR fileno () conforms to POSIX.1-2001 and POSIX.1-2008. diff --git a/man3/fexecve.3 b/man3/fexecve.3 index f61cc8ba6d..c13d8c7207 100644 --- a/man3/fexecve.3 +++ b/man3/fexecve.3 @@ -103,7 +103,7 @@ T{ .BR fexecve () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008. This function is not specified in POSIX.1-2001, @@ -121,7 +121,7 @@ needs to be mounted and available at the time of the call. .\" With the addition of the execveat(2), fexecve() can be implemented .\" even where /proc is unavailable. Review future glibc releases to .\" see if the implementation is changed to use execveat(2). - +.PP The idea behind .BR fexecve () is to allow the caller to verify (checksum) the contents of @@ -138,7 +138,7 @@ of a file could be changed between the checksumming and the call to .BR fexecve (); for that, the solution is to ensure that the permissions on the file prevent it from being modified by malicious users. - +.PP The natural idiom when using .BR fexecve () is to set the close-on-exec flag on diff --git a/man3/fflush.3 b/man3/fflush.3 index 5493829cf5..51cc00451c 100644 --- a/man3/fflush.3 +++ b/man3/fflush.3 @@ -55,13 +55,13 @@ For output streams, forces a write of all user-space buffered data for the given output or update .I stream via the stream's underlying write function. - +.PP For input streams associated with seekable files (e.g., disk files, but not pipes or terminals), .BR fflush () discards any buffered data that has been fetched from the underlying file, but has not been consumed by the application. - +.PP The open status of the stream is unaffected. .PP If the @@ -109,7 +109,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C89, C99, POSIX.1-2001, POSIX.1-2008. - +.PP POSIX.1-2001 did not specify the behavior for flushing of input streams, but the behavior is specified in POSIX.1-2008. .SH NOTES diff --git a/man3/ffs.3 b/man3/ffs.3 index 15ab23b4a2..d3bde8cb06 100644 --- a/man3/ffs.3 +++ b/man3/ffs.3 @@ -107,7 +107,7 @@ T} Thread safety MT-Safe .SH CONFORMING TO .BR ffs (): POSIX.1-2001, POSIX.1-2008, 4.3BSD. - +.PP The .BR ffsl () and diff --git a/man3/fgetc.3 b/man3/fgetc.3 index 8d6e2a5768..b98d233ed8 100644 --- a/man3/fgetc.3 +++ b/man3/fgetc.3 @@ -138,10 +138,10 @@ T{ .BR ungetc () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99. - +.PP It is not advisable to mix calls to input functions from the .I stdio library with low-level calls to diff --git a/man3/finite.3 b/man3/finite.3 index 019e801629..9252515213 100644 --- a/man3/finite.3 +++ b/man3/finite.3 @@ -99,7 +99,7 @@ functions return a nonzero value if .I x is neither infinite nor a "not-a-number" (NaN) value, and 0 otherwise. - +.PP The .BR isnan (), .BR isnanf (), @@ -109,7 +109,7 @@ functions return a nonzero value if .I x is a NaN value, and 0 otherwise. - +.PP The .BR isinf (), .BR isinff (), diff --git a/man3/floor.3 b/man3/floor.3 index 77ac37df65..549c66cf49 100644 --- a/man3/floor.3 +++ b/man3/floor.3 @@ -57,7 +57,7 @@ _ISOC99_SOURCE || _POSIX_C_SOURCE\ >=\ 200112L .SH DESCRIPTION These functions return the largest integral value that is not greater than .IR x . - +.PP For example, .IR floor(0.5) is 0.0, and @@ -66,7 +66,7 @@ is \-1.0. .SH RETURN VALUE These functions return the floor of .IR x . - +.PP If .I x is integral, +0, \-0, NaN, or an infinity, @@ -91,7 +91,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/fma.3 b/man3/fma.3 index 388676f231..813b802814 100644 --- a/man3/fma.3 +++ b/man3/fma.3 @@ -48,13 +48,13 @@ current rounding mode (see These functions return the value of .IR x " * " y " + " z , rounded as one ternary operation. - +.PP If .I x or .I y is a NaN, a NaN is returned. - +.PP If .I x times @@ -64,7 +64,7 @@ is an exact infinity, and is an infinity with the opposite sign, a domain error occurs, and a NaN is returned. - +.PP .\" POSIX.1-2008 allows some possible differences for the following two .\" domain error cases, but on Linux they are treated the same (AFAICS). .\" Nevertheless, we'll mirror POSIX.1 and describe the two cases @@ -80,7 +80,7 @@ a domain error occurs, and a NaN is returned. .\" POSIX.1 says that a NaN or an implementation-defined value shall .\" be returned for this case. - +.PP If one of .I x or @@ -91,7 +91,7 @@ is a NaN, .\" POSIX.1 makes the domain error optional for this case. a domain error occurs, and a NaN is returned. - +.PP If .I x times @@ -100,11 +100,11 @@ is not an infinity times zero (or vice versa), and .I z is a NaN, a NaN is returned. - +.PP If the result overflows, a range error occurs, and an infinity with the correct sign is returned. - +.PP If the result underflows, a range error occurs, and a signed 0 is returned. diff --git a/man3/fmax.3 b/man3/fmax.3 index 2d9ad26bb6..ce5112ec46 100644 --- a/man3/fmax.3 +++ b/man3/fmax.3 @@ -43,9 +43,9 @@ These functions return the maximum of .I x and .IR y . - +.PP If one argument is a NaN, the other argument is returned. - +.PP If both arguments are NaN, a NaN is returned. .SH ERRORS No errors occur. diff --git a/man3/fmemopen.3 b/man3/fmemopen.3 index e918b0e169..8d73693278 100644 --- a/man3/fmemopen.3 +++ b/man3/fmemopen.3 @@ -40,7 +40,7 @@ function opens a stream that permits the access specified by The stream allows I/O to be performed on the string or memory buffer pointed to by .IR buf . - +.PP The .I mode argument specifies the semantics of I/O on the stream, @@ -113,7 +113,7 @@ buffer .I size counts that byte) to allow for this. - +.PP In a stream opened for reading, null bytes (\(aq\\0\(aq) in the buffer do not cause read operations to return an end-of-file indication. @@ -121,11 +121,11 @@ A read from the buffer will indicate end-of-file only when the current buffer position advances .I size bytes past the start of the buffer. - +.PP Write operations take place either at the current position (for modes other than append), or at the current size of the stream (for append modes). - +.PP Attempts to write more than .I size bytes to the buffer result in an error. @@ -135,7 +135,7 @@ By default, such errors will be visible buffer is flushed. Disabling buffering with the following call may be useful to detect errors at the time of an output operation: - +.PP setbuf(stream, NULL); .SH RETURN VALUE Upon successful completion, @@ -161,12 +161,12 @@ T{ .BR fmemopen (), T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008. This function is not specified in POSIX.1-2001, and is not widely available on other systems. - +.PP POSIX.1-2008 specifies that \(aqb\(aq in .IR mode shall be ignored. @@ -180,7 +180,7 @@ returned by this function (i.e., .BR fileno (3) will return an error if called on the returned stream). - +.PP With version 2.22, binary mode (see below) was removed, many longstanding bugs in the implementation of .BR fmemopen () @@ -199,7 +199,7 @@ writes don't implicitly add a terminating null byte, and is relative to the end of the buffer (i.e., the value specified by the .I size argument), rather than the current string length. - +.PP An API bug afflicted the implementation of binary mode: to specify binary mode, the \(aqb\(aq must be the .I second @@ -211,7 +211,7 @@ This is inconsistent with the treatment of .IR mode by .BR fopen (3). - +.PP Binary mode was removed in glibc 2.22; a \(aqb\(aq specified in .I mode has no effect. @@ -226,7 +226,7 @@ fails with the error It would be more consistent if this case successfully created a stream that then returned end-of-file on the first attempt at reading; since version 2.22, the glibc implementation provides that behavior. - +.PP In versions of glibc before 2.22, specifying append mode ("a" or "a+") for .BR fmemopen () @@ -236,7 +236,7 @@ sets the initial buffer position to the first null byte, but the end of the stream) does not force subsequent writes to append at the end of the stream. This bug is fixed in glibc 2.22. - +.PP In versions of glibc before 2.22, if the .I mode argument to @@ -253,7 +253,7 @@ However, in this case the glibc .BR fmemopen () sets the buffer position to \-1. This bug is fixed in glibc 2.22. - +.PP In versions of glibc before 2.22, .\" https://sourceware.org/bugzilla/show_bug.cgi?id=14292 when a call to @@ -270,7 +270,7 @@ was .IR subtracted from the end-of-stream position, instead of being added. This bug is fixed in glibc 2.22. - +.PP The glibc 2.9 addition of "binary" mode for .BR fmemopen () .\" http://sourceware.org/bugzilla/show_bug.cgi?id=6544 diff --git a/man3/fmin.3 b/man3/fmin.3 index acd153d111..657c5cb7d3 100644 --- a/man3/fmin.3 +++ b/man3/fmin.3 @@ -43,9 +43,9 @@ These functions return the minimum of .I x and .IR y . - +.PP If one argument is a NaN, the other argument is returned. - +.PP If both arguments are NaN, a NaN is returned. .SH ERRORS No errors occur. diff --git a/man3/fmod.3 b/man3/fmod.3 index 633167b490..d0b222bf8f 100644 --- a/man3/fmod.3 +++ b/man3/fmod.3 @@ -89,25 +89,25 @@ such that the returned value has the same sign as .I x and a magnitude less than the magnitude of .IR y . - +.PP If .I x or .I y is a NaN, a NaN is returned. - +.PP If .I x is an infinity, a domain error occurs, and a NaN is returned. - +.PP If .I y is zero, a domain error occurs, and a NaN is returned. - +.PP If .I x is +0 (\-0), and @@ -155,7 +155,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/fmtmsg.3 b/man3/fmtmsg.3 index 95ad3f78fd..59c1756ff6 100644 --- a/man3/fmtmsg.3 +++ b/man3/fmtmsg.3 @@ -243,7 +243,7 @@ Before glibc 2.16, the .BR fmtmsg () function uses a static variable that is not protected, so it is not thread-safe. - +.PP Since glibc 2.16, .\" Modified in commit 7724defcf8873116fe4efab256596861eef21a94 the @@ -259,7 +259,7 @@ and environment variables and .B SEV_LEVEL come from System V. - +.PP The function .BR fmtmsg () and the environment variable diff --git a/man3/fopen.3 b/man3/fopen.3 index 36c251a9e2..967396de07 100644 --- a/man3/fopen.3 +++ b/man3/fopen.3 @@ -202,7 +202,7 @@ The argument is used just as in the .BR fopen () function. - +.PP If the .I pathname argument is a null pointer, @@ -213,7 +213,7 @@ that is, .BR freopen () reopens the pathname that is associated with the stream. The specification for this behavior was added in the C99 standard, which says: - +.PP .RS In this case, the file descriptor associated with the stream need not be closed @@ -303,7 +303,7 @@ T} Thread safety MT-Safe .BR fopen (), .BR freopen (): POSIX.1-2001, POSIX.1-2008, C89, C99. - +.PP .BR fdopen (): POSIX.1-2001, POSIX.1-2008. .SH NOTES @@ -364,9 +364,9 @@ and support the following syntax in .IR mode : - +.PP .BI " ,ccs=" string - +.PP The given .I string is taken as the name of a coded character set and diff --git a/man3/fopencookie.3 b/man3/fopencookie.3 index cecc96e76c..7a0d0882da 100644 --- a/man3/fopencookie.3 +++ b/man3/fopencookie.3 @@ -46,7 +46,7 @@ is used to implement .BR fmemopen (3), which provides a stream interface to data that is stored in a buffer in memory. - +.PP In order to create a custom stream the programmer must: .IP * 3 Implement four "hook" functions that are used internally by the @@ -75,14 +75,14 @@ function serves a purpose similar to it opens a new stream and returns a pointer to a .I FILE object that is used to operate on that stream. - +.PP The .I cookie argument is a pointer to the caller's cookie structure that is to be associated with the new stream. This pointer is supplied as the first argument when the standard I/O library invokes any of the hook functions described below. - +.PP The .I mode argument serves the same purpose as for @@ -98,7 +98,7 @@ and See .BR fopen (3) for details. - +.PP The .I io_funcs argument is a structure that contains four fields pointing to the @@ -121,9 +121,9 @@ The four fields are as follows: .I cookie_read_function_t *read This function implements read operations for the stream. When called, it receives three arguments: - +.IP ssize_t read(void *cookie, char *buf, size_t size); - +.IP The .I buf and @@ -138,7 +138,7 @@ function should return the number of bytes copied into The .I read function should update the stream offset appropriately. - +.IP If .I *read is a null pointer, @@ -147,9 +147,9 @@ then reads from the custom stream always return end of file. .I cookie_write_function_t *write This function implements write operations for the stream. When called, it receives three arguments: - +.IP ssize_t write(void *cookie, const char *buf, size_t size); - +.IP The .I buf and @@ -165,7 +165,7 @@ or 0 on error. The .I write function should update the stream offset appropriately. - +.IP If .I *write is a null pointer, @@ -174,9 +174,9 @@ then output to the stream is discarded. .I cookie_seek_function_t *seek This function implements seek operations on the stream. When called, it receives three arguments: - +.IP int seek(void *cookie, off64_t *offset, int whence); - +.IP The .I *offset argument specifies the new file offset depending on which @@ -203,11 +203,11 @@ Before returning, the function should update .I *offset to indicate the new stream offset. - +.IP As its function result, the .I seek function should return 0 on success, and \-1 on error. - +.IP If .I *seek is a null pointer, @@ -218,20 +218,20 @@ This function closes the stream. The hook function can do things such as freeing buffers allocated for the stream. When called, it receives one argument: - +.IP int close(void *cookie); - +.IP The .I cookie argument is the cookie that the programmer supplied when calling .BR fopencookie (). - +.IP As its function result, the .I close function should return 0 on success, and .B EOF on error. - +.IP If .I *close is NULL, then no special action is performed when the stream is closed. diff --git a/man3/fpclassify.3 b/man3/fpclassify.3 index 2eb47ff970..76fd59a06f 100644 --- a/man3/fpclassify.3 +++ b/man3/fpclassify.3 @@ -128,7 +128,7 @@ T} Thread safety MT-Safe .ad .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. - +.PP For .BR isinf (), the standards merely say that the return value is nonzero diff --git a/man3/fpurge.3 b/man3/fpurge.3 index 7f9d87d06c..627ffa364d 100644 --- a/man3/fpurge.3 +++ b/man3/fpurge.3 @@ -79,7 +79,7 @@ T{ .BR __fpurge () T} Thread safety MT-Safe race:stream .TE - +.sp 1 .SH CONFORMING TO These functions are nonstandard and not portable. The function diff --git a/man3/fputwc.3 b/man3/fputwc.3 index 62b39d52a3..3557f5c683 100644 --- a/man3/fputwc.3 +++ b/man3/fputwc.3 @@ -78,7 +78,7 @@ T{ .BR putwc () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/fputws.3 b/man3/fputws.3 index 3c491a267c..7e8ccf8b06 100644 --- a/man3/fputws.3 +++ b/man3/fputws.3 @@ -52,7 +52,7 @@ T{ .BR fputws () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/frexp.3 b/man3/frexp.3 index 862de9c178..51be5f5c13 100644 --- a/man3/frexp.3 +++ b/man3/frexp.3 @@ -77,20 +77,20 @@ the normalized fraction is times a power of two, and its absolute value is always in the range 1/2 (inclusive) to 1 (exclusive), that is, [0.5,1). - +.PP If .I x is zero, then the normalized fraction is zero and zero is stored in .IR exp . - +.PP If .I x is a NaN, a NaN is returned, and the value of .I *exp is unspecified. - +.PP If .I x is positive infinity (negative infinity), @@ -115,7 +115,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/fseek.3 b/man3/fseek.3 index ecde452328..dde79aa77c 100644 --- a/man3/fseek.3 +++ b/man3/fseek.3 @@ -183,7 +183,7 @@ T{ .BR fsetpos () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99. .SH SEE ALSO diff --git a/man3/fseeko.3 b/man3/fseeko.3 index b5a283cfd4..6793633ede 100644 --- a/man3/fseeko.3 +++ b/man3/fseeko.3 @@ -111,7 +111,7 @@ T{ .BR ftello () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SUSv2. .SH SEE ALSO diff --git a/man3/ftime.3 b/man3/ftime.3 index 8e32ceaae4..4ac01e5ce8 100644 --- a/man3/ftime.3 +++ b/man3/ftime.3 @@ -83,7 +83,7 @@ T} Thread safety MT-Safe 4.2BSD, POSIX.1-2001. POSIX.1-2008 removes the specification of .BR ftime (). - +.PP This function is obsolete. Don't use it. If the time in seconds diff --git a/man3/fts.3 b/man3/fts.3 index 37a9b97728..536ab72d95 100644 --- a/man3/fts.3 +++ b/man3/fts.3 @@ -77,7 +77,7 @@ The function .BR fts_children () returns a pointer to a linked list of structures, each of which describes one of the files contained in a directory in the hierarchy. - +.PP In general, directories are visited two distinguishable times; in preorder (before any of their descendants are visited) and in postorder (after all of their descendants have been visited). @@ -104,7 +104,7 @@ hierarchy. In this manual page, "file" and "FTSENT structure" are generally interchangeable. - +.PP The .I FTSENT structure contains fields describing a file. @@ -666,7 +666,7 @@ The .BR fts_set () function returns 0 on success, and \-1 if an error occurs. - +.PP The .I instr argument is either 0 (meaning "do nothing") or one of the following values: @@ -809,7 +809,7 @@ T{ .BR fts_children () T} Thread safety MT-Unsafe .TE - +.sp 1 .SH CONFORMING TO 4.4BSD. .SH BUGS diff --git a/man3/ftw.3 b/man3/ftw.3 index 93980e85f4..fb7fc85f37 100644 --- a/man3/ftw.3 +++ b/man3/ftw.3 @@ -67,7 +67,7 @@ located under the directory \fIdirpath\fP, and calls \fIfn\fP() once for each entry in the tree. By default, directories are handled before the files and subdirectories they contain (preorder traversal). - +.PP To avoid using up all of the calling process's file descriptors, \fInopenfd\fP specifies the maximum number of directories that .BR nftw () @@ -80,7 +80,7 @@ directories have to be closed and reopened. .BR nftw () uses at most one file descriptor for each level in the directory tree. - +.PP For each entry found in the tree, .BR nftw () calls @@ -108,7 +108,7 @@ structure returned by a call to .BR stat (2) for .IR fpath . - +.PP The .I typeflag argument passed to @@ -230,7 +230,7 @@ have the handler set a global flag that is checked by \fIfn\fP(). \fIDon't\fP use .BR longjmp (3) unless the program is going to terminate. - +.PP The \fIflags\fP argument of .BR nftw () is formed by ORing zero or more of the @@ -275,7 +275,7 @@ to return immediately with the return value .PP Other return values could be associated with new actions in the future; \fIfn\fP() should not return values other than those listed above. - +.PP The feature test macro .B _GNU_SOURCE must be defined @@ -349,14 +349,14 @@ and (possibly) .BR FTW_SL . .SH RETURN VALUE These functions return 0 on success, and \-1 if an error occurs. - +.PP If \fIfn\fP() returns nonzero, then the tree walk is terminated and the value returned by \fIfn\fP() is returned as the result of .BR ftw () or .BR nftw (). - +.PP If .BR nftw () is called with the \fBFTW_ACTIONRETVAL\fP flag, @@ -382,7 +382,7 @@ T{ .BR ftw () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SVr4, SUSv1. POSIX.1-2008 marks diff --git a/man3/futimes.3 b/man3/futimes.3 index db9a7f03e7..815f7d41ca 100644 --- a/man3/futimes.3 +++ b/man3/futimes.3 @@ -53,7 +53,7 @@ with the difference that the file whose timestamps are to be changed is specified via a file descriptor, .IR fd , rather than via a pathname. - +.PP .BR lutimes () changes the access and modification times of a file in the same way as .BR utimes (2), diff --git a/man3/gamma.3 b/man3/gamma.3 index 760bf31a00..c6d69160bd 100644 --- a/man3/gamma.3 +++ b/man3/gamma.3 @@ -46,7 +46,7 @@ These functions are deprecated: instead, use either the or the .BR lgamma (3) functions, as appropriate. - +.PP For the definition of the Gamma function, see .BR tgamma (3). .SS *BSD version diff --git a/man3/gcvt.3 b/man3/gcvt.3 index 87c7908eea..d83843cfa8 100644 --- a/man3/gcvt.3 +++ b/man3/gcvt.3 @@ -85,7 +85,7 @@ T{ .BR gcvt () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO Marked as LEGACY in POSIX.1-2001. POSIX.1-2008 removes the specification of diff --git a/man3/get_nprocs_conf.3 b/man3/get_nprocs_conf.3 index 59d8dc6ed7..574aeef10f 100644 --- a/man3/get_nprocs_conf.3 +++ b/man3/get_nprocs_conf.3 @@ -36,7 +36,7 @@ get_nprocs, get_nprocs_conf \- get number of processors The function .BR get_nprocs_conf () returns the number of processors configured by the operating system. - +.PP The function .BR get_nprocs () returns the number of processors currently available in the system. @@ -59,7 +59,7 @@ T{ .BR get_nprocs_conf () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are GNU extensions. .SH NOTES @@ -69,7 +69,7 @@ implementation of these functions is rather expensive, since they open and parse files in the .I /sys filesystem each time they are called. - +.PP The following .BR sysconf (3) calls make use of the functions documented on this page @@ -85,7 +85,7 @@ The following example shows how and .BR get_nprocs_conf () can be used. - +.PP .nf #include <stdlib.h> #include <stdio.h> @@ -100,4 +100,4 @@ main(int argc, char *argv[]) exit(EXIT_SUCCESS); } .fi - +.PP diff --git a/man3/get_phys_pages.3 b/man3/get_phys_pages.3 index 6f5561e129..4ab0bcff0c 100644 --- a/man3/get_phys_pages.3 +++ b/man3/get_phys_pages.3 @@ -36,7 +36,7 @@ page counts The function .BR get_phys_pages () returns the total number of physical pages of memory available on the system. - +.PP The function .BR get_avphys_pages () returns the number of currently available physical pages of memory on the @@ -63,12 +63,12 @@ and .I MemFree fields of .IR /proc/meminfo . - +.PP The following .BR sysconf (3) calls provide a portable means of obtaining the same information as the functions described on this page. - +.PP .nf total_pages = sysconf(_SC_PHYS_PAGES); /* total pages */ avl_pages = sysconf(_SC_AVPHYS_PAGES); /* available pages */ @@ -79,7 +79,7 @@ The following example shows how and .BR get_avphys_pages () can be used. - +.PP .nf #include <stdio.h> #include <stdlib.h> diff --git a/man3/getaddrinfo.3 b/man3/getaddrinfo.3 index 3c95ad6278..d7bf8b650c 100644 --- a/man3/getaddrinfo.3 +++ b/man3/getaddrinfo.3 @@ -302,7 +302,7 @@ and returns a pointer to the start of the list in The items in the linked list are linked by the .I ai_next field. - +.PP There are several reasons why the linked list may have more than one .I addrinfo @@ -339,7 +339,7 @@ official name of the host. .\" structure was set pointing to the canonical name; that was .\" more than POSIX.1-2001 specified, or other implementations provided. .\" MTK, Aug 05 - +.PP The remaining fields of each returned .I addrinfo structure are initialized as follows: @@ -438,7 +438,7 @@ If this flag is specified, then the node name given in .I node is converted to IDN format if necessary. The source encoding is that of the current locale. - +.IP If the input name contains non-ASCII characters, then the IDN encoding is used. Those parts of the node name (delimited by dots) that contain @@ -462,7 +462,7 @@ node corresponding to the structure value passed back. The return value is an exact copy of the value returned by the name resolution function. - +.IP If the name is encoded using ACE, then it will contain the .I xn\-\- prefix for one or more components of the name. @@ -607,7 +607,7 @@ T{ .BR gai_strerror () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. The @@ -618,7 +618,7 @@ function is documented in RFC\ 2553. supports the .IB address % scope-id notation for specifying the IPv6 scope-ID. - +.PP .BR AI_ADDRCONFIG , .BR AI_ALL , and @@ -626,7 +626,7 @@ and are available since glibc 2.3.3. .B AI_NUMERICSERV is available since glibc 2.3.4. - +.PP According to POSIX.1, specifying .\" POSIX.1-2001, POSIX.1-2008 .I hints diff --git a/man3/getaddrinfo_a.3 b/man3/getaddrinfo_a.3 index 3eabd01fc2..b00a461f33 100644 --- a/man3/getaddrinfo_a.3 +++ b/man3/getaddrinfo_a.3 @@ -55,7 +55,7 @@ function performs the same task as .BR getaddrinfo (3), but allows multiple name look-ups to be performed asynchronously, with optional notification on completion of look-up operations. - +.PP The .I mode argument has one of the following values: @@ -97,7 +97,7 @@ struct gaicb { }; .fi .in - +.PP The elements of this structure correspond to the arguments of .BR getaddrinfo (3). Thus, @@ -126,7 +126,7 @@ The .I addrinfo structure referenced by the last two elements is described in .BR getaddrinfo (3). - +.PP When .I mode is specified as @@ -178,7 +178,7 @@ it may be useful to point .IR sevp\->sigev_value.sival_ptr to .IR list . - +.PP The .BR gai_suspend () function suspends execution of the calling thread, @@ -213,7 +213,7 @@ No explicit indication of which request was completed is given; you must determine which request(s) have completed by iterating with .BR gai_error () over the list of requests. - +.PP The .BR gai_error () function returns the status of the request @@ -223,7 +223,7 @@ either if the request was not completed yet, 0 if it was handled successfully, or an error code if the request could not be resolved. - +.PP The .BR gai_cancel () function cancels the request @@ -285,7 +285,7 @@ for an unfinished look-up request, or the error code .B EAI_CANCELED if the request has been canceled explicitly before it could be finished. - +.PP The .BR gai_cancel () function can return one of these values: @@ -318,7 +318,7 @@ T{ .BR gai_cancel () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are GNU extensions; they first appeared in glibc in version 2.2.3. @@ -437,7 +437,7 @@ $ \fB./a.out\fP .in .PP The program source is as follows: - +.PP .nf #define _GNU_SOURCE #include <netdb.h> diff --git a/man3/getauxval.3 b/man3/getauxval.3 index ec3d68cbbf..5da548dd4c 100644 --- a/man3/getauxval.3 +++ b/man3/getauxval.3 @@ -40,7 +40,7 @@ function retrieves values from the auxiliary vector, a mechanism that the kernel's ELF binary loader uses to pass certain information to user space when a program is executed. - +.PP Each entry in the auxiliary vector consists of a pair of values: a type that identifies what this entry represents, and a value for that type. @@ -48,7 +48,7 @@ Given the argument .IR type , .BR getauxval () returns the corresponding value. - +.PP The value returned for each .I type is given in the following list. @@ -219,7 +219,7 @@ that allows the kernel to communicate a certain set of standard information that the dynamic linker usually or always needs. In some cases, the same information could be obtained by system calls, but using the auxiliary vector is cheaper. - +.PP The auxiliary vector resides just above the argument list and environment in the process address space. The auxiliary vector supplied to a program can be viewed by setting the diff --git a/man3/getcwd.3 b/man3/getcwd.3 index 556b959eb4..879e2dd006 100644 --- a/man3/getcwd.3 +++ b/man3/getcwd.3 @@ -78,7 +78,7 @@ the calling process. The pathname is returned as the function result and via the argument .IR buf , if present. - +.PP If the current directory is not below the root directory of the current process (e.g., because the process set a new filesystem root using .BR chroot (2) @@ -92,7 +92,7 @@ When dealing with paths from untrusted sources, callers of these functions should consider checking whether the returned path starts with '/' or '(' to avoid misinterpreting an unreachable path as a relative path. - +.PP The .BR getcwd () function copies an absolute pathname of the current working directory @@ -128,7 +128,7 @@ is allocated as big as necessary. The caller should .BR free (3) the returned buffer. - +.PP .BR get_current_dir_name () will .BR malloc (3) @@ -141,7 +141,7 @@ is set, and its value is correct, then that value will be returned. The caller should .BR free (3) the returned buffer. - +.PP .BR getwd () does not .BR malloc (3) @@ -175,7 +175,7 @@ and .BR getwd () this is the same value as .IR buf . - +.PP On failure, these functions return NULL, and .I errno is set to indicate the error. @@ -245,7 +245,7 @@ Note however that POSIX.1-2001 leaves the behavior of unspecified if .I buf is NULL. - +.PP .BR getwd () is present in POSIX.1-2001, but marked LEGACY. POSIX.1-2008 removes the specification of @@ -256,7 +256,7 @@ instead. POSIX.1-2001 does not define any errors for .BR getwd (). - +.PP .BR get_current_dir_name () is a GNU extension. .SH NOTES diff --git a/man3/getdate.3 b/man3/getdate.3 index f483636865..eb6891e71f 100644 --- a/man3/getdate.3 +++ b/man3/getdate.3 @@ -75,7 +75,7 @@ This structure is allocated in static storage, and consequently it will be overwritten by further calls to .BR getdate (). - +.PP In contrast to .BR strptime (3), (which has a @@ -87,11 +87,11 @@ whose full pathname is given in the environment variable .BR DATEMSK . The first line in the file that matches the given input string is used for the conversion. - +.PP The matching is done case insensitively. Superfluous whitespace, either in the pattern or in the string to be converted, is ignored. - +.PP The conversion specifications that a pattern can contain are those given for .BR strptime (3). One more conversion specification is specified in POSIX.1-2001: @@ -125,7 +125,7 @@ hour, minute and second are taken. .LP If no date is given, but we know the hour, then that hour is taken to be the first such hour equal to or after the current hour. - +.PP .BR getdate_r () is a GNU extension that provides a reentrant version of .BR getdate (). @@ -146,7 +146,7 @@ to one of the error numbers shown below. Changes to .I errno are unspecified. - +.PP On success .BR getdate_r () returns 0; @@ -235,7 +235,7 @@ and for each call displays the values in the fields of the returned .I tm structure. The following shell session demonstrates the operation of the program: - +.PP .in +4n .nf .RB "$" " TFILE=$PWD/tfile" diff --git a/man3/getentropy.3 b/man3/getentropy.3 index afb7369cf7..407d0ccda8 100644 --- a/man3/getentropy.3 +++ b/man3/getentropy.3 @@ -53,7 +53,7 @@ at the location pointed to by The maximum permitted value for the .I length argument is 256. - +.PP A successful call to .BR getentropy () always provides the requested number of bytes of entropy. @@ -96,19 +96,19 @@ The .BR getentropy () function is implemented using .BR getrandom (2). - +.PP Whereas the glibc wrapper makes .BR getrandom (2) a cancellation point, .BR getentropy () is not a cancellation point. - +.PP .BR getentropy () is also declared in .BR <sys/random.h> . (No feature test macro need be defined to obtain the declaration from that header file.) - +.PP A call to .BR getentropy () may block if the system has just booted and the kernel has diff --git a/man3/getenv.3 b/man3/getenv.3 index 4200884fc6..3a38847e8f 100644 --- a/man3/getenv.3 +++ b/man3/getenv.3 @@ -58,7 +58,7 @@ environment variable and returns a pointer to the corresponding .I value string. - +.PP The GNU-specific .BR secure_getenv () function is just like @@ -78,7 +78,7 @@ the process has a nonempty permitted capability set. .PP Secure execution may also be required if triggered by some Linux security modules. - +.PP The .BR secure_getenv () function is intended for use in general-purpose libraries @@ -109,18 +109,18 @@ T} Thread safety MT-Safe env .SH CONFORMING TO .BR getenv (): POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. - +.PP .BR secure_getenv () is a GNU extension. .SH NOTES The strings in the environment list are of the form \fIname=value\fP. - +.PP As typically implemented, .BR getenv () returns a pointer to a string within the environment list. The caller must take care not to modify this string, since that would change the environment of the process. - +.PP The implementation of .BR getenv () is not required to be reentrant. @@ -133,7 +133,7 @@ and can be modified by a subsequent call to .BR setenv (3), or .BR unsetenv (3). - +.PP The "secure execution" mode of .BR secure_getenv () is controlled by the diff --git a/man3/getfsent.3 b/man3/getfsent.3 index e62aba081f..40a9993483 100644 --- a/man3/getfsent.3 +++ b/man3/getfsent.3 @@ -65,7 +65,7 @@ Here the field contains (on a *BSD system) one of the five strings "rw", "rq", "ro", "sw", "xx" (read-write, read-write with quota, read-only, swap, ignore). - +.PP The function .BR setfsent () opens the file when required and positions it at the first line. diff --git a/man3/getgrent_r.3 b/man3/getgrent_r.3 index 1320910f5b..452df644c0 100644 --- a/man3/getgrent_r.3 +++ b/man3/getgrent_r.3 @@ -132,7 +132,7 @@ T{ .BR fgetgrent_r () T} Thread safety MT-Safe .TE - +.sp 1 In the above table, .I grent in diff --git a/man3/getgrnam.3 b/man3/getgrnam.3 index dfb470e5d3..61be7abd07 100644 --- a/man3/getgrnam.3 +++ b/man3/getgrnam.3 @@ -123,9 +123,9 @@ was found or an error occurred) is stored in .IR *result . .PP The call - +.PP sysconf(_SC_GETGR_R_SIZE_MAX) - +.PP returns either \-1, without changing .IR errno , or an initial suggested size for diff --git a/man3/getgrouplist.3 b/man3/getgrouplist.3 index 7948c39c32..3373536f06 100644 --- a/man3/getgrouplist.3 +++ b/man3/getgrouplist.3 @@ -58,7 +58,7 @@ Up to .I *ngroups of these groups are returned in the array .IR groups . - +.PP If it was not among the groups defined for .I user in the group database, then @@ -68,7 +68,7 @@ is included in the list of groups returned by typically this argument is specified as the group ID from the password record for .IR user . - +.PP The .I ngroups argument is a value-result argument: @@ -86,7 +86,7 @@ is a member is less than or equal to then the value .I *ngroups is returned. - +.PP If the user is a member of more than .I *ngroups groups, then diff --git a/man3/gethostbyname.3 b/man3/gethostbyname.3 index 49b6e56e5b..9859cfdf3a 100644 --- a/man3/gethostbyname.3 +++ b/man3/gethostbyname.3 @@ -107,7 +107,9 @@ _DEFAULT_SOURCE Glibc versions up to and including 2.19: _BSD_SOURCE || _SVID_SOURCE .RE - +.PD +.PP +.PD 0 .BR herror (), .BR hstrerror (): .RS 4 @@ -121,7 +123,9 @@ _BSD_SOURCE || _SVID_SOURCE Before glibc 2.8: none .RE - +.PD +.PP +.PD 0 .BR h_errno : .RS 4 .TP 4 @@ -150,7 +154,7 @@ Applications should use and .BR gai_strerror (3) instead. - +.PP The .BR gethostbyname () function returns a structure of type @@ -251,7 +255,7 @@ In glibc 2.4 and earlier, the keyword was used to control the order of host lookups as defined in .IR /etc/host.conf .RB ( host.conf (5)). - +.PP .PP The \fIhostent\fP structure is defined in \fI<netdb.h>\fP as follows: .sp @@ -394,7 +398,7 @@ T{ .BR gethostbyname2_r () T} Thread safety MT-Safe env locale .TE - +.sp 1 In the above table, .I hostent in diff --git a/man3/gethostid.3 b/man3/gethostid.3 index 0d3062ca27..5ce9619260 100644 --- a/man3/gethostid.3 +++ b/man3/gethostid.3 @@ -70,7 +70,7 @@ This normally resembles the Internet address for the local machine, as returned by .BR gethostbyname (3), and thus usually never needs to be set. - +.PP The .BR sethostid () call is restricted to the superuser. @@ -78,7 +78,7 @@ call is restricted to the superuser. .BR gethostid () returns the 32-bit identifier for the current host as set by .BR sethostid (). - +.PP On success, .BR sethostid () returns 0; on error, \-1 is returned, and @@ -110,14 +110,14 @@ T{ .BR sethostid () T} Thread safety MT-Unsafe const:hostid .TE - +.sp 1 .SH CONFORMING TO 4.2BSD; these functions were dropped in 4.4BSD. SVr4 includes .BR gethostid () but not .BR sethostid (). - +.PP POSIX.1-2001 and POSIX.1-2008 specify .BR gethostid () but not @@ -131,7 +131,7 @@ is stored in the file .I /var/adm/hostid was used.) .\" libc5 used /etc/hostid; libc4 didn't have these functions - +.PP In the glibc implementation, if .BR gethostid () cannot open the file containing the host ID, diff --git a/man3/getifaddrs.3 b/man3/getifaddrs.3 index 5082625aba..e57a43075a 100644 --- a/man3/getifaddrs.3 +++ b/man3/getifaddrs.3 @@ -180,7 +180,7 @@ T{ .BR freeifaddrs () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO Not in POSIX.1. This function first appeared in BSDi and is diff --git a/man3/getline.3 b/man3/getline.3 index c32ef68ac9..a6cb0a4f52 100644 --- a/man3/getline.3 +++ b/man3/getline.3 @@ -62,7 +62,7 @@ storing the address of the buffer containing the text into .IR "*lineptr" . The buffer is null-terminated and includes the newline character, if one was found. - +.PP If .I "*lineptr" is set to NULL and @@ -74,7 +74,7 @@ This buffer should be freed by the user program even if .BR getline () failed. - +.PP Alternatively, before calling .BR getline (), .I "*lineptr" @@ -92,13 +92,13 @@ updating and .I "*n" as necessary. - +.PP In either case, on a successful call, .I "*lineptr" and .I "*n" will be updated to reflect the buffer address and allocated size respectively. - +.PP .BR getdelim () works like .BR getline (), @@ -118,7 +118,7 @@ return the number of characters read, including the delimiter character, but not including the terminating null byte (\(aq\\0\(aq). This value can be used to handle embedded null bytes in the line read. - +.PP Both functions return \-1 on failure to read a line (including end-of-file condition). In the event of an error, @@ -150,7 +150,7 @@ T{ .BR getdelim () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO Both .BR getline () diff --git a/man3/getlogin.3 b/man3/getlogin.3 index 9020623274..b79fe2c3ae 100644 --- a/man3/getlogin.3 +++ b/man3/getlogin.3 @@ -170,7 +170,7 @@ T{ .BR cuserid () T} Thread safety MT-Unsafe race:cuserid/!string locale .TE - +.sp 1 In the above table, .I utent in @@ -192,7 +192,7 @@ so we use race:utent to remind users. and .BR getlogin_r (): POSIX.1-2001, POSIX.1-2008. - +.PP System V has a .BR cuserid () function which uses the real diff --git a/man3/getmntent.3 b/man3/getmntent.3 index 1743eb2524..1ccbe35c3b 100644 --- a/man3/getmntent.3 +++ b/man3/getmntent.3 @@ -162,7 +162,7 @@ struct mntent { }; .fi .in - +.PP Since fields in the mtab and fstab files are separated by whitespace, octal escapes are used to represent the characters space (\e040), tab (\e011), newline (\e012), and backslash (\e\e) in those files diff --git a/man3/getnameinfo.3 b/man3/getnameinfo.3 index 0e5e05b020..5678cd04ee 100644 --- a/man3/getnameinfo.3 +++ b/man3/getnameinfo.3 @@ -45,7 +45,7 @@ but unlike those functions, .BR getnameinfo () is reentrant and allows programs to eliminate IPv4-versus-IPv6 dependencies. - +.PP The .I addr argument is a pointer to a generic socket address structure @@ -68,7 +68,7 @@ respectively) into which .BR getnameinfo () places null-terminated strings containing the host and service names respectively. - +.PP The caller can specify that no hostname (or no service name) is required by providing a NULL .I host @@ -81,7 +81,7 @@ argument or a zero argument. However, at least one of hostname or service name must be requested. - +.PP The .I flags argument modifies the behavior of @@ -217,7 +217,7 @@ T{ .BR getnameinfo () T} Thread safety MT-Safe env locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, RFC\ 2553. .SH NOTES @@ -232,7 +232,7 @@ defines the constants #define NI_MAXSERV 32 .fi .in - +.PP Since glibc 2.8, these definitions are exposed only if suitable feature test macros are defined, namely: @@ -251,7 +251,7 @@ in recent versions of BIND's header file. The latter is a guess based on the services listed in the current Assigned Numbers RFC. - +.PP Before glibc version 2.2, the .I hostlen and @@ -263,7 +263,7 @@ The following code tries to get the numeric hostname and service name, for a given socket address. Note that there is no hardcoded reference to a particular address family. - +.PP .in +4n .nf struct sockaddr *addr; /* input */ @@ -275,10 +275,10 @@ if (getnameinfo(addr, addrlen, hbuf, sizeof(hbuf), sbuf, printf("host=%s, serv=%s\en", hbuf, sbuf); .fi .in - +.PP The following version checks if the socket address has a reverse address mapping. - +.PP .in +4n .nf struct sockaddr *addr; /* input */ @@ -312,17 +312,17 @@ can be found in .BR services (5), .BR hostname (7), .BR named (8) - +.PP R. Gilligan, S. Thomson, J. Bound and W. Stevens, .IR "Basic Socket Interface Extensions for IPv6" , RFC\ 2553, March 1999. - +.PP Tatsuya Jinmei and Atsushi Onoe, .IR "An Extension of Format for IPv6 Scoped Addresses" , internet draft, work in progress .UR ftp://ftp.ietf.org\:/internet\-drafts\:/draft\-ietf\-ipngwg\-scopedaddr\-format\-02.txt .UE . - +.PP Craig Metz, .IR "Protocol Independence Using the Sockets API" , Proceedings of the freenix track: diff --git a/man3/getnetent.3 b/man3/getnetent.3 index 8231818111..f616005b6f 100644 --- a/man3/getnetent.3 +++ b/man3/getnetent.3 @@ -181,7 +181,7 @@ MT-Unsafe race:netent env locale T} .TE - +.sp 1 In the above table, .I netent in diff --git a/man3/getnetent_r.3 b/man3/getnetent_r.3 index 9bb26c457d..9ccb44ef23 100644 --- a/man3/getnetent_r.3 +++ b/man3/getnetent_r.3 @@ -77,13 +77,13 @@ structure is returned, and in the function calling signature and return value. This manual page describes just the differences from the nonreentrant functions. - +.PP Instead of returning a pointer to a statically allocated .I netent structure as the function result, these functions copy the structure into the location pointed to by .IR result_buf . - +.PP The .I buf array is used to store the string fields pointed to by the returned @@ -100,7 +100,7 @@ and the caller must try again with a larger buffer. (A buffer of length 1024 bytes should be sufficient for most applications.) .\" I can find no information on the required/recommended buffer size; .\" the nonreentrant functions use a 1024 byte buffer -- mtk. - +.PP If the function call successfully obtains a network record, then .I *result is set pointing to @@ -108,7 +108,7 @@ is set pointing to otherwise, .I *result is set to NULL. - +.PP The buffer pointed to by .I h_errnop is used to return the value that would be stored in the global variable @@ -119,7 +119,7 @@ by the nonreentrant versions of these functions. .SH RETURN VALUE On success, these functions return 0. On error, they return one of the positive error numbers listed in ERRORS. - +.PP On error, record not found .RB ( getnetbyname_r (), .BR getnetbyaddr_r ()), diff --git a/man3/getopt.3 b/man3/getopt.3 index d37e572b18..2900b0c66a 100644 --- a/man3/getopt.3 +++ b/man3/getopt.3 @@ -353,11 +353,11 @@ because we permute them. We pretend they're .I const in the prototype to be compatible with other systems. - +.IP The use of \(aq+\(aq and \(aq\-\(aq in .I optstring is a GNU extension. - +.IP On some older implementations, .BR getopt () was declared in diff --git a/man3/getprotoent.3 b/man3/getprotoent.3 index 545c096466..b0c41a45e5 100644 --- a/man3/getprotoent.3 +++ b/man3/getprotoent.3 @@ -176,7 +176,7 @@ MT-Unsafe race:protoent locale T} .TE - +.sp 1 In the above table, .I protoent in diff --git a/man3/getprotoent_r.3 b/man3/getprotoent_r.3 index 7b1d583a6d..6939daa201 100644 --- a/man3/getprotoent_r.3 +++ b/man3/getprotoent_r.3 @@ -74,13 +74,13 @@ structure is returned, and in the function calling signature and return value. This manual page describes just the differences from the nonreentrant functions. - +.PP Instead of returning a pointer to a statically allocated .I protoent structure as the function result, these functions copy the structure into the location pointed to by .IR result_buf . - +.PP The .I buf array is used to store the string fields pointed to by the returned @@ -98,7 +98,7 @@ and the caller must try again with a larger buffer. .\" I can find no information on the required/recommended buffer size; .\" the nonreentrant functions use a 1024 byte buffer. .\" The 1024 byte value is also what the Solaris man page suggests. -- mtk - +.PP If the function call successfully obtains a protocol record, then .I *result is set pointing to @@ -109,7 +109,7 @@ is set to NULL. .SH RETURN VALUE On success, these functions return 0. On error, they return one of the positive error numbers listed in ERRORS. - +.PP On error, record not found .RB ( getprotobyname_r (), .BR getprotobynumber_r ()), @@ -145,7 +145,7 @@ T{ .BR getprotobynumber_r () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO These functions are GNU extensions. Functions with similar names exist on some other systems, diff --git a/man3/getpw.3 b/man3/getpw.3 index 13e8d02bdd..9d6b121d3b 100644 --- a/man3/getpw.3 +++ b/man3/getpw.3 @@ -75,7 +75,7 @@ The function returns 0 on success; on error, it returns \-1, and .I errno is set to indicate the error. - +.PP If .I uid is not found in the password database, @@ -115,7 +115,7 @@ T{ .BR getpw () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO SVr2. .SH BUGS diff --git a/man3/getpwent.3 b/man3/getpwent.3 index 4de22ee81b..132102a851 100644 --- a/man3/getpwent.3 +++ b/man3/getpwent.3 @@ -115,7 +115,7 @@ is set appropriately. If one wants to check .I errno after the call, it should be set to zero before the call. - +.PP The return value may point to a static area, and may be overwritten by subsequent calls to .BR getpwent (), @@ -173,7 +173,7 @@ T{ .BR endpwent () T} Thread safety MT-Unsafe race:pwent locale .TE - +.sp 1 In the above table, .I pwent in diff --git a/man3/getpwent_r.3 b/man3/getpwent_r.3 index a8791a3d5d..752c69b9e1 100644 --- a/man3/getpwent_r.3 +++ b/man3/getpwent_r.3 @@ -85,7 +85,7 @@ struct passwd { .PP For more information about the fields of this structure, see .BR passwd (5). - +.PP The nonreentrant functions return a pointer to static storage, where this static storage contains further pointers to user name, password, gecos field, home directory and shell. @@ -134,7 +134,7 @@ T{ .BR fgetpwent_r () T} Thread safety MT-Safe .TE - +.sp 1 In the above table, .I pwent in diff --git a/man3/getpwnam.3 b/man3/getpwnam.3 index e9b9d34b36..d965a90473 100644 --- a/man3/getpwnam.3 +++ b/man3/getpwnam.3 @@ -127,9 +127,9 @@ was found or an error occurred) is stored in .IR *result . .PP The call - +.PP sysconf(_SC_GETPW_R_SIZE_MAX) - +.PP returns either \-1, without changing .IR errno , or an initial suggested size for @@ -257,7 +257,7 @@ situation: 0, ENOENT, EBADF, ESRCH, EWOULDBLOCK, EPERM, and probably others. .\" FreeBSD 4.8, OpenBSD 3.2, NetBSD 1.6 - give EPERM .\" SunOS 5.8 - gives EBADF .\" Tru64 5.1b, HP-UX-11i, SunOS 5.7 - give 0 - +.PP The .I pw_dir field contains the name of the initial working directory of the user. @@ -280,7 +280,7 @@ The program below demonstrates the use of .BR getpwnam_r () to find the full username and user ID for the username supplied as a command-line argument. - +.PP .nf #include <pwd.h> #include <stdio.h> diff --git a/man3/getrpcent.3 b/man3/getrpcent.3 index bb44b10044..a126a4e2df 100644 --- a/man3/getrpcent.3 +++ b/man3/getrpcent.3 @@ -118,7 +118,7 @@ T{ .BR endrpcent () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO Not in POSIX.1. Present on the BSDs, Solaris, and many other systems. diff --git a/man3/getrpcent_r.3 b/man3/getrpcent_r.3 index 46b90757bd..4cc9e001f0 100644 --- a/man3/getrpcent_r.3 +++ b/man3/getrpcent_r.3 @@ -74,13 +74,13 @@ structure is returned, and in the function calling signature and return value. This manual page describes just the differences from the nonreentrant functions. - +.PP Instead of returning a pointer to a statically allocated .I rpcent structure as the function result, these functions copy the structure into the location pointed to by .IR result_buf . - +.PP The .I buf array is used to store the string fields pointed to by the returned @@ -97,7 +97,7 @@ and the caller must try again with a larger buffer. (A buffer of length 1024 bytes should be sufficient for most applications.) .\" I can find no information on the required/recommended buffer size; .\" the nonreentrant functions use a 1024 byte buffer -- mtk. - +.PP If the function call successfully obtains an RPC record, then .I *result is set pointing to @@ -108,7 +108,7 @@ is set to NULL. .SH RETURN VALUE On success, these functions return 0. On error, they return one of the positive error numbers listed in ERRORS. - +.PP On error, record not found .RB ( getrpcbyname_r (), .BR getrpcbynumber_r ()), diff --git a/man3/getrpcport.3 b/man3/getrpcport.3 index 89530658f5..044ee3c5e9 100644 --- a/man3/getrpcport.3 +++ b/man3/getrpcport.3 @@ -47,7 +47,7 @@ T{ .BR getrpcport () T} Thread safety MT-Safe env locale .TE - +.sp 1 .SH CONFORMING TO Not in POSIX.1. Present on the BSDs, Solaris, and many other systems. diff --git a/man3/gets.3 b/man3/gets.3 index fda48ba2fd..ca2df58054 100644 --- a/man3/gets.3 +++ b/man3/gets.3 @@ -37,7 +37,7 @@ gets \- get a string from standard input (DEPRECATED) .fi .SH DESCRIPTION .IR "Never use this function" . - +.PP .BR gets () reads a line from .I stdin @@ -67,10 +67,10 @@ T{ .BR gets () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C89, C99, POSIX.1-2001. - +.PP LSB deprecates .BR gets (). POSIX.1-2008 marks @@ -96,7 +96,7 @@ It has been used to break computer security. Use .BR fgets () instead. - +.PP For more information, see CWE-242 (aka "Use of Inherently Dangerous Function") at http://cwe.mitre.org/data/definitions/242.html diff --git a/man3/getservent.3 b/man3/getservent.3 index eb64e18ce1..78b9861c11 100644 --- a/man3/getservent.3 +++ b/man3/getservent.3 @@ -193,7 +193,7 @@ MT-Unsafe race:servent locale T} .TE - +.sp 1 In the above table, .I servent in diff --git a/man3/getservent_r.3 b/man3/getservent_r.3 index 55275eda06..ec1a39f9d9 100644 --- a/man3/getservent_r.3 +++ b/man3/getservent_r.3 @@ -74,13 +74,13 @@ structure is returned, and in the function calling signature and return value. This manual page describes just the differences from the nonreentrant functions. - +.PP Instead of returning a pointer to a statically allocated .I servent structure as the function result, these functions copy the structure into the location pointed to by .IR result_buf . - +.PP The .I buf array is used to store the string fields pointed to by the returned @@ -97,7 +97,7 @@ and the caller must try again with a larger buffer. (A buffer of length 1024 bytes should be sufficient for most applications.) .\" I can find no information on the required/recommended buffer size; .\" the nonreentrant functions use a 1024 byte buffer -- mtk. - +.PP If the function call successfully obtains a service record, then .I *result is set pointing to @@ -108,7 +108,7 @@ is set to NULL. .SH RETURN VALUE On success, these functions return 0. On error, they return one of the positive error numbers listed in errors. - +.PP On error, record not found .RB ( getservbyname_r (), .BR getservbyport_r ()), diff --git a/man3/getspnam.3 b/man3/getspnam.3 index 2a7d1535c9..dc4e81e3ae 100644 --- a/man3/getspnam.3 +++ b/man3/getspnam.3 @@ -291,7 +291,7 @@ T{ .BR fgetspent_r () T} Thread safety MT-Safe .TE - +.sp 1 In the above table, .I getspent in diff --git a/man3/getsubopt.3 b/man3/getsubopt.3 index a7992bf90a..deca6bc7ec 100644 --- a/man3/getsubopt.3 +++ b/man3/getsubopt.3 @@ -65,7 +65,7 @@ that might be passed in .in +4n .B ro,name=xyz .in - +.PP The .I tokens argument is a pointer to a NULL-terminated array of pointers to the tokens that @@ -74,7 +74,7 @@ will look for in .IR optionp . The tokens should be distinct, null-terminated strings containing at least one character, with no embedded equal signs or commas. - +.PP Each call to .BR getsubopt () returns information about the next unprocessed suboption in @@ -95,11 +95,11 @@ The first comma in is overwritten with a null byte, so .I *valuep is precisely the "value string" for that suboption. - +.PP If the suboption is recognized, but no value string was found, .I *valuep is set to NULL. - +.PP When .BR getsubopt () returns, @@ -119,7 +119,7 @@ Otherwise, \-1 is returned and is the entire .IB name [= value ] string. - +.PP Since .I *optionp is changed, the first suboption before the call to @@ -141,7 +141,7 @@ T} Thread safety MT-Safe .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES - +.PP Since .BR getsubopt () overwrites any commas it finds in the string @@ -149,7 +149,7 @@ overwrites any commas it finds in the string that string must be writable; it cannot be a string constant. .SH EXAMPLE The following program expects suboptions following a "\-o" option. - +.PP .nf #define _XOPEN_SOURCE 500 #include <stdlib.h> diff --git a/man3/getttyent.3 b/man3/getttyent.3 index 0222e6e4e5..548cd948c8 100644 --- a/man3/getttyent.3 +++ b/man3/getttyent.3 @@ -22,22 +22,22 @@ These functions provide an interface to the file .B _PATH_TTYS (e.g., .IR /etc/ttys ). - +.PP The function .BR setttyent () opens the file or rewinds it if already open. - +.PP The function .BR endttyent () closes the file. - +.PP The function .BR getttynam () searches for a given terminal name in the file. It returns a pointer to a .I ttyent structure (description below). - +.PP The function .BR getttyent () opens the file @@ -60,7 +60,7 @@ struct ttyent { }; .fi .in - +.PP .I ty_status can be: .br diff --git a/man3/getutent.3 b/man3/getutent.3 index 31446dfa7e..582b564347 100644 --- a/man3/getutent.3 +++ b/man3/getutent.3 @@ -51,7 +51,7 @@ utmpname \- access utmp file entries .SH DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see CONFORMING TO. - +.PP .BR utmpname () sets the name of the utmp-format file for the other utmp functions to access. @@ -124,16 +124,16 @@ return a pointer to a \fIstruct utmp\fP on success, and NULL on failure (which includes the "record not found" case). This \fIstruct utmp\fP is allocated in static storage, and may be overwritten by subsequent calls. - +.PP On success .BR pututline () returns .IR ut ; on failure, it returns NULL. - +.PP .BR utmpname () returns 0 if the new name was successfully stored, or \-1 on failure. - +.PP In the event of an error, these functions .I errno set to indicate the cause. @@ -194,7 +194,7 @@ T{ .BR utmpname () T} Thread safety MT-Unsafe race:utent .TE - +.sp 1 In the above table, .I utent in diff --git a/man3/getwchar.3 b/man3/getwchar.3 index de255751b4..c296919cb4 100644 --- a/man3/getwchar.3 +++ b/man3/getwchar.3 @@ -64,7 +64,7 @@ T{ .BR getwchar () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/glob.3 b/man3/glob.3 index 1d622d7f2f..767e2cd64a 100644 --- a/man3/glob.3 +++ b/man3/glob.3 @@ -292,7 +292,7 @@ T{ .BR globfree () T} Thread safety MT-Safe .TE - +.sp 1 In the above table, .I utent in diff --git a/man3/gnu_get_libc_version.3 b/man3/gnu_get_libc_version.3 index df8534349a..650a32d22c 100644 --- a/man3/gnu_get_libc_version.3 +++ b/man3/gnu_get_libc_version.3 @@ -37,7 +37,7 @@ gnu_get_libc_version, gnu_get_libc_release \- get glibc version and release The function .BR gnu_get_libc_version () returns a string that identifies the glibc version available on the system. - +.PP The function .BR gnu_get_libc_release () returns a string indicates the release status of the glibc version diff --git a/man3/grantpt.3 b/man3/grantpt.3 index 27b9293dde..0eb3dc9584 100644 --- a/man3/grantpt.3 +++ b/man3/grantpt.3 @@ -79,13 +79,13 @@ T{ .BR grantpt () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES This is part of the UNIX 98 pseudoterminal support, see .BR pts (4). - +.PP Many systems implement this function via a set-user-ID helper binary called "pt_chown". On Linux systems with a devpts filesystem (present since Linux 2.2), diff --git a/man3/gsignal.3 b/man3/gsignal.3 index 3533162c69..30a5c657db 100644 --- a/man3/gsignal.3 +++ b/man3/gsignal.3 @@ -110,7 +110,7 @@ T{ .BR ssignal () T} Thread safety MT-Safe sigintr .TE - +.sp 1 .SH CONFORMING TO These functions are available under AIX, DG/UX, HP-UX, SCO, Solaris, Tru64. They are called obsolete under most of these systems, and are diff --git a/man3/hash.3 b/man3/hash.3 index fcc45daef4..bd5dfbd57b 100644 --- a/man3/hash.3 +++ b/man3/hash.3 @@ -51,7 +51,7 @@ Since version 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. - +.PP The routine .BR dbopen (3) is the library interface to database files. @@ -162,9 +162,9 @@ Only big and little endian byte order are supported. .BR dbopen (3), .BR mpool (3), .BR recno (3) - +.PP .IR "Dynamic Hash Tables" , Per-Ake Larson, Communications of the ACM, April 1988. - +.PP .IR "A New Hash Package for UNIX" , Margo Seltzer, USENIX Proceedings, Winter 1991. diff --git a/man3/hsearch.3 b/man3/hsearch.3 index 3644729d53..1a934aac66 100644 --- a/man3/hsearch.3 +++ b/man3/hsearch.3 @@ -66,7 +66,7 @@ and allow the caller to create and manage a hash search table containing entries consisting of a key (a string) and associated data. Using these functions, only one hash table can be used at a time. - +.PP The three functions .BR hcreate_r (), .BR hsearch_r (), @@ -80,7 +80,7 @@ on which the function is to operate. The programmer should treat this structure as opaque (i.e., do not attempt to directly access or modify the fields in this structure). - +.PP First a hash table must be created using .BR hcreate (). The argument \fInel\fP specifies the maximum number of entries @@ -89,7 +89,7 @@ in the table. The implementation may adjust this value upward to improve the performance of the resulting hash table. .\" e.g., in glibc it is raised to the next higher prime number - +.PP The .BR hcreate_r () function performs the same task as @@ -100,7 +100,7 @@ The structure pointed to by .I htab must be zeroed before the first call to .BR hcreate_r (). - +.PP The function .BR hdestroy () frees the memory occupied by the hash table that was created by @@ -115,14 +115,14 @@ function performs the analogous task for a hash table described by .IR *htab , which was previously created using .BR hcreate_r (). - +.PP The .BR hsearch () function searches the hash table for an item with the same key as \fIitem\fP (where "the same" is determined using .BR strcmp (3)), and if successful returns a pointer to it. - +.PP The argument \fIitem\fP is of type \fIENTRY\fP, which is defined in \fI<search.h>\fP as follows: .in +4n @@ -138,7 +138,7 @@ typedef struct entry { The field \fIkey\fP points to a null-terminated string which is the search key. The field \fIdata\fP points to data that is associated with that key. - +.PP The argument \fIaction\fP determines what .BR hsearch () does after an unsuccessful search. @@ -157,7 +157,7 @@ is then .I data is ignored.) - +.PP The .BR hsearch_r () function is like @@ -179,7 +179,7 @@ return nonzero on success. They return 0 on error, with .I errno set to indicate the cause of the error. - +.PP On success, .BR hsearch () returns a pointer to an entry in the hash table. @@ -257,7 +257,7 @@ The functions and .BR hdestroy () are from SVr4, and are described in POSIX.1-2001 and POSIX.1-2008. - +.PP The functions .BR hcreate_r (), .BR hsearch_r (), @@ -271,7 +271,7 @@ Typically, this means that .I nel should be at least 25% larger than the maximum number of elements that the caller expects to store in the table. - +.PP The .BR hdestroy () and @@ -296,7 +296,7 @@ should not do anything for a successful search. In libc and glibc (before version 2.3), the implementation violates the specification, updating the \fIdata\fP for the given \fIkey\fP in this case. - +.PP Individual hash table entries can be added, but not deleted. .SH EXAMPLE .PP diff --git a/man3/hypot.3 b/man3/hypot.3 index 15014208f3..1b53c31868 100644 --- a/man3/hypot.3 +++ b/man3/hypot.3 @@ -79,7 +79,7 @@ and or the distance of the point .RI ( x , y ) from the origin. - +.PP The calculation is performed without undue overflow or underflow during the intermediate steps of the calculation. .\" e.g., hypot(DBL_MIN, DBL_MIN) does the right thing, as does, say @@ -90,14 +90,14 @@ with sides of length .I x and .IR y . - +.PP If .I x or .I y is an infinity, positive infinity is returned. - +.PP If .I x or @@ -105,7 +105,7 @@ or is a NaN, and the other argument is not an infinity, a NaN is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -114,7 +114,7 @@ and the functions return or .BR HUGE_VALL , respectively. - +.PP If both arguments are subnormal, and the result is subnormal, .\" Actually, could the result not be subnormal if both arguments .\" are subnormal? I think not -- mtk, Jul 2008 @@ -164,10 +164,10 @@ T{ .BR hypotl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/iconv.3 b/man3/iconv.3 index f7202701b5..2ebde98d05 100644 --- a/man3/iconv.3 +++ b/man3/iconv.3 @@ -165,7 +165,7 @@ In each series of calls to .BR iconv (), the last should be one with \fIinbuf\fP or \fI*inbuf\fP equal to NULL, in order to flush out any partially converted input. - +.PP Although .I inbuf and @@ -177,7 +177,7 @@ as C strings or as arrays of characters: the interpretation of character byte sequences is handled internally by the conversion functions. In some encodings, a zero byte may be a valid part of a multibyte character. - +.PP The caller of .BR iconv () must ensure that the pointers passed to the function are suitable diff --git a/man3/iconv_close.3 b/man3/iconv_close.3 index 2e44248b91..ae0ae2283e 100644 --- a/man3/iconv_close.3 +++ b/man3/iconv_close.3 @@ -48,7 +48,7 @@ T{ .BR iconv_close () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SUSv2. .SH SEE ALSO diff --git a/man3/iconv_open.3 b/man3/iconv_open.3 index a17817537a..ac8371eef7 100644 --- a/man3/iconv_open.3 +++ b/man3/iconv_open.3 @@ -114,7 +114,7 @@ T{ .BR iconv_open () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SUSv2. .SH SEE ALSO diff --git a/man3/if_nameindex.3 b/man3/if_nameindex.3 index 6099f36bdf..a36f68de1c 100644 --- a/man3/if_nameindex.3 +++ b/man3/if_nameindex.3 @@ -115,16 +115,16 @@ T{ .BR if_freenameindex () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, RFC\ 3493. - +.PP This function first appeared in BSDi. .SH EXAMPLE The program below demonstrates the use of the functions described on this page. An example of the output this program might produce is the following: - +.PP .in +4n .nf $ \fB./a.out\fI diff --git a/man3/if_nametoindex.3 b/man3/if_nametoindex.3 index 414646f5e2..f6e341af94 100644 --- a/man3/if_nametoindex.3 +++ b/man3/if_nametoindex.3 @@ -40,7 +40,7 @@ The function returns the index of the network interface corresponding to the name .IR ifname . - +.PP The .BR if_indextoname () function returns the name of the network interface @@ -58,7 +58,7 @@ returns the index number of the network interface; on error, 0 is returned and .I errno is set appropriately. - +.PP On success, .BR if_indextoname () returns @@ -105,7 +105,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, RFC\ 3493. - +.PP This function first appeared in BSDi. .SH SEE ALSO .BR getifaddrs (3), diff --git a/man3/ilogb.3 b/man3/ilogb.3 index a52cd651fd..4cf42ba498 100644 --- a/man3/ilogb.3 +++ b/man3/ilogb.3 @@ -75,7 +75,7 @@ functions, cast to On success, these functions return the exponent of .IR x , as a signed integer. - +.PP If .I x is zero, then a domain error occurs, and the functions return @@ -83,14 +83,14 @@ is zero, then a domain error occurs, and the functions return .\" case, but for ilogb() it says domain error. .BR FP_ILOGB0 . .\" glibc: The numeric value is either `INT_MIN' or `-INT_MAX'. - +.PP If .I x is a NaN, then a domain error occurs, and the functions return .BR FP_ILOGBNAN . .\" glibc: The numeric value is either `INT_MIN' or `INT_MAX'. .\" On i386, FP_ILOGB0 and FP_ILOGBNAN have the same value. - +.PP If .I x is negative infinity or positive infinity, then diff --git a/man3/inet.3 b/man3/inet.3 index 59d9e88661..4100d08c17 100644 --- a/man3/inet.3 +++ b/man3/inet.3 @@ -134,7 +134,7 @@ The form that uses exactly four decimal numbers is referred to as .IR "IPv4 dotted-decimal notation" (or sometimes: .IR "IPv4 dotted-quad notation" ). - +.PP .BR inet_aton () returns 1 if the supplied string was successfully interpreted, or 0 if the string is invalid @@ -246,14 +246,14 @@ T} Thread safety MT-Safe .BR inet_addr (), .BR inet_ntoa (): POSIX.1-2001, POSIX.1-2008, 4.3BSD. - +.PP .BR inet_aton () is not specified in POSIX.1, but is available on most systems. .SH NOTES On x86 architectures, the host byte order is Least Significant Byte first (little endian), whereas the network byte order, as used on the Internet, is Most Significant Byte first (big endian). - +.PP .BR inet_lnaof (), .BR inet_netof (), and diff --git a/man3/inet_net_pton.3 b/man3/inet_net_pton.3 index 37758414b0..922eee94d8 100644 --- a/man3/inet_net_pton.3 +++ b/man3/inet_net_pton.3 @@ -61,7 +61,7 @@ _BSD_SOURCE || _SVID_SOURCE .SH DESCRIPTION These functions convert network numbers between presentation (i.e., printable) format and network (i.e., binary) format. - +.PP For both functions, .I af specifies the address family for the conversion; @@ -86,7 +86,7 @@ The .I nsize argument specifies the number of bytes available in .IR netp . - +.PP On success, .BR inet_net_pton () returns the number of bits in the network number field @@ -94,7 +94,7 @@ of the result placed in .IR netp . For a discussion of the input presentation format and the return value, see NOTES. - +.PP .IR Note : the buffer pointed to by .I netp @@ -116,7 +116,7 @@ The .I bits argument specifies the number of bits in the network number in .IR *netp . - +.PP The null-terminated presentation-format string is placed in the buffer pointed to by .IR pres . @@ -134,7 +134,7 @@ returns the number of bits in the network number. On error, it returns \-1, and .I errno is set to indicate the cause of the error. - +.PP On success, .BR inet_net_ntop () returns @@ -167,21 +167,21 @@ functions are nonstandard, but widely available. The network number may be specified either as a hexadecimal value or in dotted-decimal notation. - +.PP Hexadecimal values are indicated by an initial "0x" or "0X". The hexadecimal digits populate the nibbles (half octets) of the network number from left to right in network byte order. .\" If the hexadecimal string is short, the remaining nibbles are zeroed. - +.PP In dotted-decimal notation, up to four octets are specified, as decimal numbers separated by dots. Thus, any of the following forms are accepted: - +.PP a.b.c.d a.b.c a.b a - +.PP Each part is a number in the range 0 to 255 that populates one byte of the resulting network number, going from left to right, in network-byte (big endian) order. @@ -189,7 +189,7 @@ Where a part is omitted, the resulting byte in the network number is zero. .\" Reading other man pages, some other implementations treat .\" 'c' in a.b.c as a 16-bit number that populates right-most two bytes .\" 'b' in a.b as a 24-bit number that populates right-most three bytes - +.PP For either hexadecimal or dotted-decimal format, the network number can optionally be followed by a slash and a number in the range 0 to 32, @@ -258,7 +258,7 @@ It then uses .BR inet_net_ntop () to convert the binary form back to presentation format, and displays the resulting string. - +.PP In order to demonstrate that .BR inet_net_pton () may not write to all bytes of its @@ -272,11 +272,11 @@ the program displays all of the bytes of the buffer returned by .BR inet_net_pton () allowing the user to see which bytes have not been touched by .BR inet_net_pton (). - +.PP An example run, showing that .BR inet_net_pton () infers the number of bits in the network number: - +.PP .in +4n .nf $ \fB./a.out 193.168\fP @@ -285,11 +285,11 @@ inet_net_ntop() yielded: 193.168.0/24 Raw address: c1a80000 .fi .in - +.PP Demonstrate that .BR inet_net_pton () does not zero out unused bytes in its result buffer: - +.PP .in +4n .nf $ \fB./a.out 193.168 0xffffffff\fP @@ -298,13 +298,13 @@ inet_net_ntop() yielded: 193.168.0/24 Raw address: c1a800ff .fi .in - +.PP Demonstrate that .BR inet_net_pton () will widen the inferred size of the network number, if the supplied number of bytes in the presentation string exceeds the inferred value: - +.PP .in +4n .nf $ \fB./a.out 193.168.1.128\fP @@ -313,13 +313,13 @@ inet_net_ntop() yielded: 193.168.1.128/32 Raw address: c1a80180 .fi .in - +.PP Explicitly specifying the size of the network number overrides any inference about its size (but any extra bytes that are explicitly specified will still be used by .BR inet_net_pton (): to populate the result buffer): - +.PP .in +4n .nf $ \fB./a.out 193.168.1.128/24\fP diff --git a/man3/inet_ntop.3 b/man3/inet_ntop.3 index 3fad5890d6..139f7bd5eb 100644 --- a/man3/inet_ntop.3 +++ b/man3/inet_ntop.3 @@ -109,7 +109,7 @@ T{ .BR inet_ntop () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. Note that RFC\ 2553 defines a prototype where the last argument diff --git a/man3/initgroups.3 b/man3/initgroups.3 index b984f0512d..305bbec3dd 100644 --- a/man3/initgroups.3 +++ b/man3/initgroups.3 @@ -64,7 +64,7 @@ The additional group .I group is also added to the list. - +.PP The .I user argument must be non-NULL. @@ -100,7 +100,7 @@ T{ .BR initgroups () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO SVr4, 4.3BSD. .SH SEE ALSO diff --git a/man3/insque.3 b/man3/insque.3 index a882102bd2..454ac178da 100644 --- a/man3/insque.3 +++ b/man3/insque.3 @@ -72,19 +72,19 @@ backward pointer. The linked list may be linear (i.e., NULL forward pointer at the end of the list and NULL backward pointer at the start of the list) or circular. - +.PP The .BR insque () function inserts the element pointed to by \fIelem\fP immediately after the element pointed to by \fIprev\fP. - +.PP If the list is linear, then the call .I "insque(elem, NULL)" can be used to insert the initial list element, and the call sets the forward and backward pointers of .I elem to NULL. - +.PP If the list is circular, the caller should ensure that the forward and backward pointers of the first element are initialized to point to that element, @@ -93,7 +93,7 @@ and the argument of the .BR insque () call should also point to the element. - +.PP The .BR remque () function removes the element pointed to by \fIelem\fP from the @@ -111,7 +111,7 @@ T{ .BR remque () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES @@ -119,7 +119,7 @@ On ancient systems, .\" e.g., SunOS, Linux libc4 and libc5 the arguments of these functions were of type \fIstruct qelem *\fP, defined as: - +.PP .in +4n .nf struct qelem { @@ -129,12 +129,12 @@ struct qelem { }; .fi .in - +.PP This is still what you will get if .B _GNU_SOURCE is defined before including \fI<search.h>\fP. - +.PP The location of the prototypes for these functions differs among several versions of UNIX. The above is the POSIX version. diff --git a/man3/intro.3 b/man3/intro.3 index 1eb60320b0..1bdd07e344 100644 --- a/man3/intro.3 +++ b/man3/intro.3 @@ -30,7 +30,7 @@ intro \- introduction to library functions Section 3 of the manual describes all library functions excluding the library functions (system call wrappers) described in Section 2, which implement system calls. - +.PP Many of the functions described in the section are part of the Standard C Library .RI ( libc ). @@ -47,7 +47,7 @@ and .IR \-lrt , respectively, for the aforementioned libraries). - +.PP In some cases, the programmer must define a feature test macro in order to obtain the declaration of a function from the header file specified diff --git a/man3/isalpha.3 b/man3/isalpha.3 index 661d4a5be5..fbbfa5a68b 100644 --- a/man3/isalpha.3 +++ b/man3/isalpha.3 @@ -82,12 +82,12 @@ _XOPEN_SOURCE || /* Glibc since 2.19: */ _DEFAULT_SOURCE || /* Glibc versions <= 2.19: */ _SVID_SOURCE .RE - +.PP .BR isblank (): .RS 4 _ISOC99_SOURCE || _POSIX_C_SOURCE\ >=\ 200112L .RE - +.PP .BR isalnum_l (), .BR isalpha_l (), .BR isblank_l (), @@ -110,7 +110,7 @@ Before glibc 2.10: _GNU_SOURCE .RE .PD - +.PP .BR isascii_l (): .PD 0 .RS 4 @@ -133,7 +133,7 @@ or falls into a certain character class according to the specified locale. The functions without the "_l" suffix perform the check based on the current locale. - +.PP The functions with the "_l" suffix perform the check based on the locale specified by the locale object .IR locale . @@ -144,7 +144,7 @@ is the special locale object (see .BR duplocale (3)) or is not a valid locale object handle. - +.PP The list below explains the operation of the functions without the "_l" suffix; the functions with the "_l" suffix differ only in using the locale object @@ -288,12 +288,12 @@ and .BR isblank (). C99 specifies all of the preceding functions, except .BR isascii (). - +.PP POSIX.1-2008 marks .BR isascii () as obsolete, noting that it cannot be used portably in a localized application. - +.PP POSIX.1-2008 specifies .BR isalnum_l (), .BR isalpha_l (), @@ -308,7 +308,7 @@ POSIX.1-2008 specifies .BR isupper_l (), and .BR isxdigit_l (). - +.PP .BR isascii_l () is a GNU extension. .SH NOTES @@ -325,7 +325,7 @@ is of type it must be cast to .IR "unsigned char" , as in the following example: - +.PP .nf .in +4n char c; @@ -333,7 +333,7 @@ char c; res = toupper((unsigned char) c); .in .fi - +.PP This is necessary because .I char may be the equivalent of @@ -343,7 +343,7 @@ converting to .IR int , yielding a value that is outside the range of .IR "unsigned char" . - +.PP The details of what characters belong to which class depend on the locale. For example, diff --git a/man3/isgreater.3 b/man3/isgreater.3 index b0ff18ce0a..c50e8e19ef 100644 --- a/man3/isgreater.3 +++ b/man3/isgreater.3 @@ -48,7 +48,7 @@ The normal relational operations (like will fail if one of the operands is NaN. This will cause an exception. To avoid this, C99 defines the macros listed below. - +.PP These macros are guaranteed to evaluate their arguments only once. The arguments must be of real floating-point type (note: do not pass integer values as arguments to these macros, since the arguments will @@ -109,7 +109,7 @@ The macros other than .BR isunordered () return the result of the relational comparison; these macros return 0 if either argument is a NaN. - +.PP .BR isunordered () returns 1 if .IR x @@ -126,11 +126,11 @@ values. On success, these functions return the appropriate Bessel value of the first kind for .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is too large in magnitude, diff --git a/man3/key_setsecret.3 b/man3/key_setsecret.3 index b6197561c3..e848a2e11f 100644 --- a/man3/key_setsecret.3 +++ b/man3/key_setsecret.3 @@ -29,29 +29,29 @@ The functions here are used within the RPC's secure authentication mechanism (AUTH_DES). There should be no need for user programs to use this functions. - +.PP The function .BR key_decryptsession () uses the (remote) server netname and takes the DES key for decrypting. It uses the public key of the server and the secret key associated with the effective UID of the calling process. - +.PP The function .BR key_encryptsession () is the inverse of .BR key_decryptsession (). It encrypts the DES keys with the public key of the server and the secret key associated with the effective UID of the calling process. - +.PP The function .BR key_gendes () is used to ask the keyserver for a secure conversation key. - +.PP The function .BR key_setsecret () is used to set the key for the effective UID of the calling process. - +.PP The function .BR key_secretkey_is_set () can be used to determine whether a key has been @@ -78,7 +78,7 @@ T{ .BR key_secretkey_is_set () T} Thread safety MT-Safe .TE - +.sp 1 .SH NOTES Note that we talk about two types of encryption here. One is asymmetric using a public and secret key. diff --git a/man3/killpg.3 b/man3/killpg.3 index c1cedae590..7515a28eef 100644 --- a/man3/killpg.3 +++ b/man3/killpg.3 @@ -68,7 +68,7 @@ to the process group See .BR signal (7) for a list of signals. - +.PP If .I pgrp is 0, @@ -77,7 +77,7 @@ sends the signal to the calling process's process group. (POSIX says: if .I pgrp is less than or equal to 1, the behavior is undefined.) - +.PP For the permissions required to send a signal to another process, see .BR kill (2). .SH RETURN VALUE diff --git a/man3/ldexp.3 b/man3/ldexp.3 index 8ea2be35f0..6d95c58d1b 100644 --- a/man3/ldexp.3 +++ b/man3/ldexp.3 @@ -69,27 +69,27 @@ by 2 raised to the power .SH RETURN VALUE On success, these functions return .IR "x * (2^exp)" . - +.PP If .I exp is zero, then .I x is returned. - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity (negative infinity), positive infinity (negative infinity) is returned. - +.PP If the result underflows, a range error occurs, and zero is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -138,7 +138,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/lgamma.3 b/man3/lgamma.3 index dc92244438..08f27337b6 100644 --- a/man3/lgamma.3 +++ b/man3/lgamma.3 @@ -97,20 +97,20 @@ have been introduced; they return the sign via the argument .IR signp . .SH RETURN VALUE On success, these functions return the natural logarithm of Gamma(x). - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is 1 or 2, +0 is returned. - +.PP If .I x is positive infinity or negative infinity, positive infinity is returned. - +.PP If .I x is a nonpositive integer, @@ -121,7 +121,7 @@ and the functions return or .RB + HUGE_VALL , respectively. - +.PP If the result overflows, a range error occurs, .\" e.g., lgamma(DBL_MAX) diff --git a/man3/lio_listio.3 b/man3/lio_listio.3 index 26fff2776f..9ed9ffa27d 100644 --- a/man3/lio_listio.3 +++ b/man3/lio_listio.3 @@ -38,7 +38,7 @@ The .BR lio_listio () function initiates the list of I/O operations described by the array .IR aiocb_list . - +.PP The .I mode operation has one of the following values: @@ -74,7 +74,7 @@ argument specifies the size of the array null pointers in .I aiocb_list are ignored. - +.PP In each control block in .IR aiocb_list , the @@ -115,7 +115,7 @@ returns 0 if all I/O operations are successfully queued. Otherwise, \-1 is returned, and .I errno is set to indicate the error. - +.PP If .I mode is @@ -125,7 +125,7 @@ returns 0 when all of the I/O operations have completed successfully. Otherwise, \-1 is returned, and .I errno is set to indicate the error. - +.PP The return status from .BR lio_listio () provides information only about the call itself, @@ -215,7 +215,7 @@ T{ .BR lio_listio () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES @@ -226,7 +226,7 @@ The buffer areas being read into or written from .\" or the control block of the operation must not be accessed during the operations or undefined results may occur. The memory areas involved must remain valid. - +.PP Simultaneous I/O operations specifying the same .I aiocb structure produce undefined results. diff --git a/man3/lockf.3 b/man3/lockf.3 index 3e454e469c..9d3175f6fb 100644 --- a/man3/lockf.3 +++ b/man3/lockf.3 @@ -170,7 +170,7 @@ POSIX.1-2001, POSIX.1-2008, SVr4. .SH SEE ALSO .BR fcntl (2), .BR flock (2) - +.PP .I locks.txt and .I mandatory-locking.txt diff --git a/man3/log.3 b/man3/log.3 index d0252d70c1..237dbe7651 100644 --- a/man3/log.3 +++ b/man3/log.3 @@ -69,21 +69,21 @@ These functions return the natural logarithm of .SH RETURN VALUE On success, these functions return the natural logarithm of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is 1, the result is +0. - +.PP If .I x is positive infinity, positive infinity is returned. - +.PP If .I x is zero, @@ -93,7 +93,7 @@ then a pole error occurs, and the functions return or .RB - HUGE_VALL , respectively. - +.PP If .I x is negative (including negative infinity), then @@ -137,7 +137,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/log10.3 b/man3/log10.3 index d4a46fe3a5..8d6f7db9c5 100644 --- a/man3/log10.3 +++ b/man3/log10.3 @@ -69,7 +69,7 @@ These functions return the base 10 logarithm of .SH RETURN VALUE On success, these functions return the base 10 logarithm of .IR x . - +.PP For special cases, including where .I x is 0, 1, negative, infinity, or NaN, see @@ -79,7 +79,7 @@ See .BR math_error (7) for information on how to determine whether an error has occurred when calling these functions. - +.PP For a discussion of the errors that can occur for these functions, see .BR log (3). .SH ATTRIBUTES @@ -98,7 +98,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/log1p.3 b/man3/log1p.3 index 9175d5d4f6..2312e37003 100644 --- a/man3/log1p.3 +++ b/man3/log1p.3 @@ -79,16 +79,16 @@ is near zero. .SH RETURN VALUE On success, these functions return the natural logarithm of .IR "(1\ +\ x)" . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity, positive infinity is returned. - +.PP If .I x is \-1, a pole error occurs, @@ -98,7 +98,7 @@ and the functions return or .RB - HUGE_VALL , respectively. - +.PP If .I x is less than \-1 (including negative infinity), @@ -155,7 +155,7 @@ Before version 2.22, the glibc implementation did not set to .B EDOM when a domain error occurred. - +.PP Before version 2.22, the glibc implementation did not set .\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=6792 .I errno diff --git a/man3/log2.3 b/man3/log2.3 index 69548180c7..a8f3e68126 100644 --- a/man3/log2.3 +++ b/man3/log2.3 @@ -68,7 +68,7 @@ These functions return the base 2 logarithm of .SH RETURN VALUE On success, these functions return the base 2 logarithm of .IR x . - +.PP For special cases, including where .I x is 0, 1, negative, infinity, or NaN, see @@ -78,7 +78,7 @@ See .BR math_error (7) for information on how to determine whether an error has occurred when calling these functions. - +.PP For a discussion of the errors that can occur for these functions, see .BR log (3). .SH VERSIONS @@ -99,7 +99,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/logb.3 b/man3/logb.3 index f918f831dd..b183fd25fd 100644 --- a/man3/logb.3 +++ b/man3/logb.3 @@ -91,12 +91,12 @@ would have if it were normalized. .SH RETURN VALUE On success, these functions return the exponent of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is zero, then a pole error occurs, and the functions return @@ -105,7 +105,7 @@ is zero, then a pole error occurs, and the functions return or .RB - HUGE_VALL , respectively. - +.PP If .I x is negative infinity or positive infinity, then diff --git a/man3/login.3 b/man3/login.3 index 7c1abe00a1..373469d79a 100644 --- a/man3/login.3 +++ b/man3/login.3 @@ -127,7 +127,7 @@ MT-Unsafe race:utent sig:ALRM timer T} .TE - +.sp 1 In the above table, .I utent in diff --git a/man3/lrint.3 b/man3/lrint.3 index a02221e357..fff5794a1e 100644 --- a/man3/lrint.3 +++ b/man3/lrint.3 @@ -61,7 +61,7 @@ _ISOC99_SOURCE || _POSIX_C_SOURCE\ >=\ 200112L These functions round their argument to the nearest integer value, using the current rounding direction (see .BR fesetround (3)). - +.PP Note that unlike the .BR rint (3) family of functions, @@ -69,7 +69,7 @@ the return type of these functions differs from that of their arguments. .SH RETURN VALUE These functions return the rounded integer value. - +.PP If .I x is a NaN or an infinity, diff --git a/man3/lround.3 b/man3/lround.3 index 6925b91cb0..a05366accf 100644 --- a/man3/lround.3 +++ b/man3/lround.3 @@ -63,7 +63,7 @@ These functions round their argument to the nearest integer value, rounding away from zero, regardless of the current rounding direction (see .BR fenv (3)). - +.PP Note that unlike the .BR round (3) and @@ -72,7 +72,7 @@ functions, the return type of these functions differs from that of their arguments. .SH RETURN VALUE These functions return the rounded integer value. - +.PP If .I x is a NaN or an infinity, diff --git a/man3/lsearch.3 b/man3/lsearch.3 index b23b742d0e..d46524a5ab 100644 --- a/man3/lsearch.3 +++ b/man3/lsearch.3 @@ -90,7 +90,7 @@ T{ .BR lsearch () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD. Present in libc since libc-4.6.27. diff --git a/man3/lseek64.3 b/man3/lseek64.3 index d365ec3081..6579ab819a 100644 --- a/man3/lseek64.3 +++ b/man3/lseek64.3 @@ -154,7 +154,7 @@ The prototype is: .sp For more details, see .BR llseek (2). - +.PP 64-bit systems don't need an .BR _llseek () system call. diff --git a/man3/makecontext.3 b/man3/makecontext.3 index 4305b6a9d0..72803dd526 100644 --- a/man3/makecontext.3 +++ b/man3/makecontext.3 @@ -61,7 +61,7 @@ the caller must allocate a new stack for this context and assign its address to \fIucp\->uc_stack\fP, and define a successor context and assign its address to \fIucp\->uc_link\fP. - +.PP When this context is later activated (using .BR setcontext (3) or @@ -133,7 +133,7 @@ to be used as the stack, regardless of the direction of growth of the stack. Thus, it is not necessary for the user program to worry about this direction. - +.PP On architectures where .I int and pointer types are the same size diff --git a/man3/makedev.3 b/man3/makedev.3 index 79f335595b..52cfff8bcf 100644 --- a/man3/makedev.3 +++ b/man3/makedev.3 @@ -41,14 +41,14 @@ a major ID, identifying the class of the device, and a minor ID, identifying a specific instance of a device in that class. A device ID is represented using the type .IR dev_t . - +.PP Given major and minor device IDs, .BR makedev () combines these to produce a device ID, returned as the function result. This device ID can be given to .BR mknod (2), for example. - +.PP The .BR major () and @@ -92,7 +92,7 @@ they have been aliases for three GNU-specific functions: and .BR gnu_dev_minor (). The latter names are exported, but the traditional names are more portable. - +.PP The BSDs expose the definitions for these macros via .IR <sys/types.h> , and glibc also exposes definitions for these macros from that diff --git a/man3/mallinfo.3 b/man3/mallinfo.3 index 8e5a909abe..13651e9074 100644 --- a/man3/mallinfo.3 +++ b/man3/mallinfo.3 @@ -119,7 +119,7 @@ T{ .BR mallinfo () T} Thread safety MT-Unsafe init const:mallopt .TE - +.sp 1 .BR mallinfo () would access some global internal objects. If modify them with non-atomically, @@ -149,7 +149,7 @@ See and .BR malloc_info (3) for alternatives that include information about other arenas. - +.PP The fields of the .I mallinfo structure are typed as @@ -163,11 +163,11 @@ The program below employs to retrieve memory allocation statistics before and after allocating and freeing some blocks of memory. The statistics are displayed on standard output. - +.PP The first two command-line arguments specify the number and size of blocks to be allocated with .BR malloc (3). - +.PP The remaining three arguments specify which of the allocated blocks should be freed with .BR free (3). @@ -181,7 +181,7 @@ of the last block to be freed (default is one greater than the maximum block number). If these three arguments are omitted, then the defaults cause all allocated blocks to be freed. - +.PP In the following example run of the program, 1000 allocations of 100 bytes are performed, and then every second allocated block is freed: diff --git a/man3/malloc_get_state.3 b/man3/malloc_get_state.3 index 4797952cb2..8cf96693d0 100644 --- a/man3/malloc_get_state.3 +++ b/man3/malloc_get_state.3 @@ -36,7 +36,7 @@ malloc_get_state, malloc_set_state \- record and restore state of malloc impleme .SH DESCRIPTION .IR Note : these function are removed in glibc version 2.25. - +.PP The .BR malloc_get_state () function records the current state of all @@ -53,7 +53,7 @@ and a pointer to that data structure is returned as the function result. (It is the caller's responsibility to .BR free (3) this memory.) - +.PP The .BR malloc_set_state () function restores the state of all @@ -68,7 +68,7 @@ returns a pointer to a newly allocated opaque data structure. On error (for example, memory could not be allocated for the data structure), .BR malloc_get_state () returns NULL. - +.PP On success, .BR malloc_set_state () returns 0. @@ -99,7 +99,7 @@ T{ .BR malloc_set_state () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are GNU extensions. .SH NOTES @@ -108,7 +108,7 @@ These functions are useful when using this implementation as part of a shared library, and the heap contents are saved/restored via some other method. This technique is used by GNU Emacs to implement its "dumping" function. - +.PP Hook function pointers are never saved or restored by these functions, with two exceptions: if malloc checking (see diff --git a/man3/malloc_info.3 b/man3/malloc_info.3 index 51a16bc55f..a8b7375605 100644 --- a/man3/malloc_info.3 +++ b/man3/malloc_info.3 @@ -41,7 +41,7 @@ The string is printed on the file stream .IR stream . The exported string includes information about all arenas (see .BR malloc (3)). - +.PP As currently implemented, .I options must be zero. @@ -72,7 +72,7 @@ T{ .BR malloc_info () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO This function is a GNU extension. .SH NOTES @@ -81,13 +81,13 @@ The memory-allocation information is provided as an XML string because the information may change over time (according to changes in the underlying implementation). The output XML string includes a version field. - +.PP The .BR open_memstream (3) function can be used to send the output of .BR malloc_info () directly into a buffer in memory, rather than to a file. - +.PP The .BR malloc_info () function is designed to address deficiencies in @@ -105,14 +105,14 @@ The third argument controls the size of the blocks to be allocated. The main thread creates blocks of this size, the second thread created by the program allocates blocks of twice this size, the third thread allocates blocks of three times this size, and so on. - +.PP The program calls .BR malloc_info () twice to display the memory-allocation state. The first call takes place before any threads are created or memory allocated. The second call is performed after all threads have allocated memory. - +.PP In the following example, the command-line arguments specify the creation of one additional thread, and both the main thread and the additional thread diff --git a/man3/malloc_stats.3 b/man3/malloc_stats.3 index 62cd0aebcb..5bf60f9e03 100644 --- a/man3/malloc_stats.3 +++ b/man3/malloc_stats.3 @@ -64,7 +64,7 @@ T{ .BR malloc_stats () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO This function is a GNU extension. .SH NOTES diff --git a/man3/malloc_trim.3 b/man3/malloc_trim.3 index 6163c4ba1d..9325395c5a 100644 --- a/man3/malloc_trim.3 +++ b/man3/malloc_trim.3 @@ -37,7 +37,7 @@ function attempts to release free memory at the top of the heap (by calling .BR sbrk (2) with a suitable argument). - +.PP The .I pad argument specifies the amount of free space to leave untrimmed @@ -69,7 +69,7 @@ T{ .BR malloc_trim () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO This function is a GNU extension. .SH NOTES @@ -81,10 +81,10 @@ and .B M_TRIM_THRESHOLD in .BR mallopt (3). - +.PP This function cannot release free memory located at places other than the top of the heap. - +.PP This function releases only memory in the main arena. .\" malloc/malloc.c::mTRIm(): .\" return result | (av == &main_arena ? sYSTRIm (pad, av) : 0); diff --git a/man3/malloc_usable_size.3 b/man3/malloc_usable_size.3 index d4e0d42ee1..8c54c4b4e1 100644 --- a/man3/malloc_usable_size.3 +++ b/man3/malloc_usable_size.3 @@ -69,7 +69,7 @@ without ill effects, this is not good programming practice: the number of excess bytes in an allocation depends on the underlying implementation. - +.PP The main use of this function is for debugging and introspection. .SH SEE ALSO .BR malloc (3) diff --git a/man3/mallopt.3 b/man3/mallopt.3 index db273ee054..efdeae69ee 100644 --- a/man3/mallopt.3 +++ b/man3/mallopt.3 @@ -41,7 +41,7 @@ The argument specifies the parameter to be modified, and .I value specifies the new value for that parameter. - +.PP The following values can be specified for .IR param : .TP @@ -56,18 +56,18 @@ therefore may have multiple concurrent memory requests. The trade-off is between the number of threads and the number of arenas. The more arenas you have, the lower the per-thread contention, but the higher the memory usage. - +.IP The default value of this parameter is 0, meaning that the limit on the number of arenas is determined according to the setting of .BR M_ARENA_TEST . - +.IP This parameter has been available since glibc 2.10 via .BR \-\-enable\-experimental\-malloc , and since glibc 2.15 by default. In some versions of the allocator there was no limit on the number of created arenas (e.g., CentOS 5, RHEL 5). - +.IP When employing newer glibc versions, applications may in some cases exhibit high contention when accessing arenas. In these cases, it may be beneficial to increase @@ -83,22 +83,22 @@ to determine a hard limit on the number of created arenas. (See .B M_ARENA_MAX for the definition of an arena.) - +.IP The computation of the arena hard limit is implementation-defined and is usually calculated as a multiple of the number of available CPUs. Once the hard limit is computed, the result is final and constrains the total number of arenas. - +.IP The default value for the .B M_ARENA_TEST parameter is 2 on systems where .IR sizeof(long) is 4; otherwise the default value is 8. - +.IP This parameter has been available since glibc 2.10 via .BR \-\-enable\-experimental\-malloc , and since glibc 2.15 by default. - +.IP The value of .B M_ARENA_TEST is not used when @@ -261,7 +261,7 @@ Subsequent reallocation of blocks of the same size can be handled very quickly by allocating from the fastbin, although memory fragmentation and the overall memory footprint of the program can increase. - +.IP The default value for this parameter is .IR "64*sizeof(size_t)/4" (i.e., 64 on 32-bit architectures). @@ -285,7 +285,7 @@ the freed bytes are set to the least significant byte of This can be useful for detecting errors where programs incorrectly rely on allocated memory being initialized to zero, or reuse values in memory that has already been freed. - +.IP The default value for this parameter is 0. .TP .BR M_TOP_PAD @@ -365,7 +365,7 @@ then the settings take precedence.) For security reasons, these variables are ignored in set-user-ID and set-group-ID programs. - +.PP The environment variables are as follows (note the trailing underscore at the end of the name of some variables): .TP @@ -465,7 +465,7 @@ but only the first of these is implemented in glibc. Specifying an invalid value for .I param does not generate an error. - +.PP A calculation error within the glibc implementation means that a call of the form: .\" FIXME . This looks buggy: @@ -488,7 +488,7 @@ where .I k is an integer. .\" Bins are multiples of 2 * sizeof(size_t) + sizeof(size_t) - +.PP If .BR mallopt () is used to set @@ -518,7 +518,7 @@ then that argument is used to set the parameter. The program then allocates a block of memory, and frees it twice (an error). - +.PP The following shell session shows what happens when we run this program under glibc, with the default value for .BR M_CHECK_ACTION : diff --git a/man3/matherr.3 b/man3/matherr.3 index 2baf30014c..7533aad7ea 100644 --- a/man3/matherr.3 +++ b/man3/matherr.3 @@ -62,7 +62,7 @@ after .BR matherr () returns, the system then returns to the math function, which in turn returns to the caller. - +.PP The .BR matherr () mechanism is supported by glibc, but is now obsolete: @@ -73,7 +73,7 @@ and This page documents the glibc .BR matherr () mechanism as an aid for maintaining and porting older applications. - +.PP To employ .BR matherr (), the programmer must define the @@ -86,7 +86,7 @@ and assign the value .B _SVID_ to the external variable .BR _LIB_VERSION . - +.PP The system provides a default version of .BR matherr (). This version does nothing, and returns zero @@ -98,7 +98,7 @@ version, which will be invoked when an exception occurs. The function is invoked with one argument, a pointer to an .I exception structure, defined as follows: - +.PP .in +4n .nf struct exception { @@ -169,7 +169,7 @@ and fields are the arguments supplied to the function .RI ( arg2 is undefined for functions that take only one argument). - +.PP The .I retval field specifies the return value that the math @@ -177,14 +177,14 @@ function will return to its caller. The programmer-defined .BR matherr () can modify this field to change the return value of the math function. - +.PP If the .BR matherr () function returns zero, then the system sets .I errno as described above, and may print an error message on standard error (see below). - +.PP If the .BR matherr () function returns a nonzero value, then the system does not set @@ -200,13 +200,13 @@ when calling .BR matherr (). The "Result" column is the default return value assigned to .IR exc\->retval . - +.PP The "Msg?" and "errno" columns describe the default behavior if .BR matherr () returns zero. If the "Msg?" columns contains "y", then the system prints an error message on standard error. - +.PP The table uses the following notations and abbreviations: .RS .nf @@ -319,12 +319,12 @@ If the optional third command-line argument is supplied, then it specifies an alternative return value that .BR matherr () should assign as the return value of the math function. - +.PP The following example run, where .BR log (3) is given an argument of 0.0, does not use .BR matherr (): - +.PP .in +4n .nf .RB "$" " ./a.out 0.0" @@ -332,11 +332,11 @@ errno: Numerical result out of range x=-inf .fi .in - +.PP In the following run, .BR matherr () is called, and returns 0: - +.PP .in +4n .nf .RB "$" " ./a.out 0.0 0" @@ -348,13 +348,13 @@ errno: Numerical argument out of domain x=-340282346638528859811704183484516925440.000000 .fi .in - +.PP The message "log: SING error" was printed by the C library. - +.PP In the following run, .BR matherr () is called, and returns a nonzero value: - +.PP .in +4n .nf .RB "$" " ./a.out 0.0 1" @@ -364,16 +364,16 @@ matherr SING exception in log() function x=-340282346638528859811704183484516925440.000000 .fi .in - +.PP In this case, the C library did not print a message, and .I errno was not set. - +.PP In the following run, .BR matherr () is called, changes the return value of the math function, and returns a nonzero value: - +.PP .in +4n .nf .RB "$" " ./a.out 0.0 1 12345.0" diff --git a/man3/mbsnrtowcs.3 b/man3/mbsnrtowcs.3 index c003bb1d6e..b3a1fe40ab 100644 --- a/man3/mbsnrtowcs.3 +++ b/man3/mbsnrtowcs.3 @@ -132,7 +132,7 @@ if the input buffer ends with an incomplete character, it is unspecified whether conversion stops at the end of the previous character (if any), or at the end of the input buffer. The glibc implementation adopts the former behavior. - +.PP If .IR dest is NULL, @@ -179,7 +179,7 @@ T{ .BR mbsnrtowcs () T} Thread safety MT-Unsafe race:mbsnrtowcs/!ps .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008. .SH NOTES diff --git a/man3/mbsrtowcs.3 b/man3/mbsrtowcs.3 index 4844e511cf..f58867e1ea 100644 --- a/man3/mbsrtowcs.3 +++ b/man3/mbsrtowcs.3 @@ -135,7 +135,7 @@ T{ .BR mbsrtowcs () T} Thread safety MT-Unsafe race:mbsrtowcs/!ps .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/mcheck.3 b/man3/mcheck.3 index 96cdba673f..24e26ef1bb 100644 --- a/man3/mcheck.3 +++ b/man3/mcheck.3 @@ -48,7 +48,7 @@ on the state of the heap. The checks can detect application errors such as freeing a block of memory more than once or corrupting the bookkeeping data structures that immediately precede a block of allocated memory. - +.PP To be effective, the .BR mcheck () function must be called before the first call to @@ -60,7 +60,7 @@ inserts an implicit call to .BR mcheck () (with a NULL argument) before the first call to a memory-allocation function. - +.PP The .BR mcheck_pedantic () function is similar to @@ -68,14 +68,14 @@ function is similar to but performs checks on all allocated blocks whenever one of the memory-allocation functions is called. This can be very slow! - +.PP The .BR mcheck_check_all () function causes an immediate check on all allocated blocks. This call is effective only if .BR mcheck () is called beforehand. - +.PP If the system detects an inconsistency in the heap, the caller-supplied function pointed to by .I abortfunc @@ -88,7 +88,7 @@ is NULL, a default function prints an error message on .IR stderr and calls .BR abort (3). - +.PP The .BR mprobe () function performs a consistency check on @@ -100,7 +100,7 @@ function should be called beforehand (otherwise .BR mprobe () returns .BR MCHECK_DISABLED ). - +.PP The following list describes the values returned by .BR mprobe () or passed as the @@ -162,7 +162,7 @@ MT-Unsafe race:mcheck const:malloc_hooks T} .TE - +.sp 1 .SH CONFORMING TO These functions are GNU extensions. .SH NOTES diff --git a/man3/memccpy.3 b/man3/memccpy.3 index dedc85bb4d..d26d1df164 100644 --- a/man3/memccpy.3 +++ b/man3/memccpy.3 @@ -50,7 +50,7 @@ stopping when the character .I c is found. - +.PP If the memory areas overlap, the results are undefined. .SH RETURN VALUE The diff --git a/man3/memchr.3 b/man3/memchr.3 index a2705678e5..b78729342e 100644 --- a/man3/memchr.3 +++ b/man3/memchr.3 @@ -78,7 +78,7 @@ except that it searches backward from the end of the bytes pointed to by .I s instead of forward from the beginning. - +.PP The .BR rawmemchr () function is similar to @@ -110,7 +110,7 @@ and functions return a pointer to the matching byte or NULL if the character does not occur in the given memory area. - +.PP The .BR rawmemchr () function returns a pointer to the matching byte, if one is found. @@ -118,7 +118,7 @@ If no matching byte is found, the result is unspecified. .SH VERSIONS .BR rawmemchr () first appeared in glibc in version 2.1. - +.PP .BR memrchr () first appeared in glibc in version 2.2. .SH ATTRIBUTES @@ -138,11 +138,11 @@ T} Thread safety MT-Safe .SH CONFORMING TO .BR memchr (): POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. - +.PP The .BR memrchr () function is a GNU extension, available since glibc 2.1.91. - +.PP The .BR rawmemchr () function is a GNU extension, available since glibc 2.1. diff --git a/man3/memcmp.3 b/man3/memcmp.3 index c8a33abe77..29897df953 100644 --- a/man3/memcmp.3 +++ b/man3/memcmp.3 @@ -49,7 +49,7 @@ function returns an integer less than, equal to, or greater than zero if the first \fIn\fP bytes of \fIs1\fP is found, respectively, to be less than, to match, or be greater than the first \fIn\fP bytes of \fIs2\fP. - +.PP For a nonzero return value, the sign is determined by the sign of the difference between the first pair of bytes (interpreted as .IR "unsigned char" ) @@ -57,7 +57,7 @@ that differ in .I s1 and .IR s2 . - +.PP If .I n is zero, the return value is zero. diff --git a/man3/memcpy.3 b/man3/memcpy.3 index d571c2399e..448f983461 100644 --- a/man3/memcpy.3 +++ b/man3/memcpy.3 @@ -80,7 +80,7 @@ in which bytes were copied from .I src to .IR dest . - +.PP This change revealed breakages in a number of applications that performed copying with overlapping areas. .\" Adobe Flash player was the highest profile example: diff --git a/man3/mkfifo.3 b/man3/mkfifo.3 index a5a7f927bc..8c952b9364 100644 --- a/man3/mkfifo.3 +++ b/man3/mkfifo.3 @@ -89,7 +89,7 @@ The function operates in exactly the same way as .BR mkfifo (), except for the differences described here. - +.PP If the pathname given in .I pathname is relative, then it is interpreted relative to the directory @@ -99,7 +99,7 @@ referred to by the file descriptor the calling process, as is done by .BR mkfifo () for a relative pathname). - +.PP If .I pathname is relative and @@ -111,7 +111,7 @@ then is interpreted relative to the current working directory of the calling process (like .BR mkfifo ()). - +.PP If .I pathname is absolute, then @@ -197,7 +197,7 @@ T} Thread safety MT-Safe .SH CONFORMING TO .BR mkfifo (): POSIX.1-2001, POSIX.1-2008. - +.PP .BR mkfifoat (): POSIX.1-2008. .SH SEE ALSO diff --git a/man3/mkstemp.3 b/man3/mkstemp.3 index 23229509c0..fa7db1fbbc 100644 --- a/man3/mkstemp.3 +++ b/man3/mkstemp.3 @@ -81,7 +81,7 @@ function generates a unique temporary filename from .IR template , creates and opens the file, and returns an open file descriptor for the file. - +.PP The last six characters of .I template must be "XXXXXX" and these are replaced with a string that makes the @@ -89,7 +89,7 @@ filename unique. Since it will be modified, .I template must not be a string constant, but should be declared as a character array. - +.PP The file is created with permissions 0600, that is, read plus write for owner only. The returned file descriptor provides both read and write access to the file. @@ -97,7 +97,7 @@ The file is opened with the .BR open (2) .B O_EXCL flag, guaranteeing that the caller is the process that creates the file. - +.PP The .BR mkostemp () function is like @@ -128,7 +128,7 @@ argument given to is unnecessary, and produces errors on some .\" Reportedly, FreeBSD systems. - +.PP The .BR mkstemps () function is like @@ -144,7 +144,7 @@ is of the form .IR "prefixXXXXXXsuffix" , and the string XXXXXX is modified as for .BR mkstemp (). - +.PP The .BR mkostemps () function is to @@ -212,12 +212,12 @@ T} Thread safety MT-Safe .SH CONFORMING TO .BR mkstemp (): 4.3BSD, POSIX.1-2001. - +.PP .BR mkstemps (): unstandardized, but appears on several other systems. .\" mkstemps() appears to be at least on the BSDs, Mac OS X, Solaris, .\" and Tru64. - +.PP .BR mkostemp () and .BR mkostemps (): @@ -229,7 +229,7 @@ This old behavior may be a security risk, especially since other UNIX flavors use 0600, and somebody might overlook this detail when porting programs. POSIX.1-2008 adds a requirement that the file be created with mode 0600. - +.PP More generally, the POSIX specification of .BR mkstemp () does not say anything diff --git a/man3/mktemp.3 b/man3/mktemp.3 index c76f1d3ad9..7ce878f7dd 100644 --- a/man3/mktemp.3 +++ b/man3/mktemp.3 @@ -65,7 +65,7 @@ _BSD_SOURCE || _SVID_SOURCE || _XOPEN_SOURCE\ >=\ 500 .SH DESCRIPTION .IR "Never use this function" ; see BUGS. - +.PP The .BR mktemp () function generates a unique temporary filename diff --git a/man3/modf.3 b/man3/modf.3 index bf37655d01..37318b955f 100644 --- a/man3/modf.3 +++ b/man3/modf.3 @@ -72,13 +72,13 @@ The integral part is stored in the location pointed to by .SH RETURN VALUE These functions return the fractional part of .IR x . - +.PP If .I x is a NaN, a NaN is returned, and .IR *iptr is set to a NaN. - +.PP If .I x is positive infinity (negative infinity), +0 (\-0) is returned, and @@ -102,7 +102,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/mpool.3 b/man3/mpool.3 index 46bfd175b7..de01e74d7a 100644 --- a/man3/mpool.3 +++ b/man3/mpool.3 @@ -66,7 +66,7 @@ Since version 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. - +.PP .I Mpool is the library interface intended to provide page oriented buffer management of files. diff --git a/man3/mq_close.3 b/man3/mq_close.3 index 886f53c90c..5c05acf13e 100644 --- a/man3/mq_close.3 +++ b/man3/mq_close.3 @@ -38,7 +38,7 @@ Link with \fI\-lrt\fP. .BR mq_close () closes the message queue descriptor .IR mqdes . - +.PP If the calling process has attached a notification request (see .RB ( mq_notify (3)) to this message queue via diff --git a/man3/mq_getattr.3 b/man3/mq_getattr.3 index f115df53c6..b157e2fa97 100644 --- a/man3/mq_getattr.3 +++ b/man3/mq_getattr.3 @@ -44,7 +44,7 @@ and respectively retrieve and modify attributes of the message queue referred to by the message queue descriptor .IR mqdes . - +.PP .BR mq_getattr () returns an .I mq_attr @@ -70,7 +70,7 @@ This field is initialized when the queue is created by .BR mq_open (3). The only flag that can appear in this field is .BR O_NONBLOCK . - +.PP The .I mq_maxmsg and @@ -91,11 +91,11 @@ Two .I /proc files that place ceilings on the values for these fields are described in .BR mq_overview (7). - +.PP The .I mq_curmsgs field returns the number of messages currently held in the queue. - +.PP .BR mq_setattr () sets message queue attributes using information supplied in the .I mq_attr @@ -168,7 +168,7 @@ in which the .I attr argument is NULL. Here is an example run of the program: - +.PP .in +4n .nf $ \fB./a.out /testq\fP @@ -176,13 +176,13 @@ Maximum # of messages on queue: 10 Maximum message size: 8192 .fi .in - +.PP Since Linux 3.5, the following .I /proc files (described in .BR mq_overview (7)) can be used to control the defaults: - +.PP .in +4n .nf $ \fBuname -sr\fP diff --git a/man3/mq_notify.3 b/man3/mq_notify.3 index dafe0919ba..0415c4a147 100644 --- a/man3/mq_notify.3 +++ b/man3/mq_notify.3 @@ -40,7 +40,7 @@ allows the calling process to register or unregister for delivery of an asynchronous notification when a new message arrives on the empty message queue referred to by the message queue descriptor .IR mqdes . - +.PP The .I sevp argument is a pointer to a @@ -98,21 +98,21 @@ for details. .PP Only one process can be registered to receive notification from a message queue. - +.PP If .I sevp is NULL, and the calling process is currently registered to receive notifications for this message queue, then the registration is removed; another process can then register to receive a message notification for this queue. - +.PP Message notification occurs only when a new message arrives and the queue was previously empty. If the queue was not empty at the time .BR mq_notify () was called, then a notification will occur only after the queue is emptied and a new message arrives. - +.PP If another process or thread is waiting to read a message from an empty queue using .BR mq_receive (3), @@ -120,7 +120,7 @@ then any message notification registration is ignored: the message is delivered to the process or thread calling .BR mq_receive (3), and the message notification registration remains in effect. - +.PP Notification occurs once: after a notification is delivered, the notification registration is removed, and another process can register for message notification. @@ -183,7 +183,7 @@ T{ .BR mq_notify () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001. .SH NOTES diff --git a/man3/mq_open.3 b/man3/mq_open.3 index d32c5e8e24..cf5c34de7f 100644 --- a/man3/mq_open.3 +++ b/man3/mq_open.3 @@ -47,7 +47,7 @@ For details of the construction of .IR name , see .BR mq_overview (7). - +.PP The .I oflag argument specifies flags that control the operation of the call. @@ -117,7 +117,7 @@ as for (Symbolic definitions for the permissions bits can be obtained by including .IR <sys/stat.h> .) The permissions settings are masked against the process umask. - +.PP The fields of the .IR "struct mq_attr" pointed to @@ -125,7 +125,7 @@ pointed to specify the maximum number of messages and the maximum size of messages that the queue will allow. This structure is defined as follows: - +.PP .in +4n .nf @@ -138,7 +138,7 @@ struct mq_attr { }; .fi .in - +.PP Only the .I mq_maxmsg and @@ -146,7 +146,7 @@ and fields are employed when calling .BR mq_open (); the values in the remaining fields are ignored. - +.PP If .I attr is NULL, then the queue is created with implementation-defined diff --git a/man3/mq_receive.3 b/man3/mq_receive.3 index e3ffb2c584..278265593b 100644 --- a/man3/mq_receive.3 +++ b/man3/mq_receive.3 @@ -73,7 +73,7 @@ If .I msg_prio is not NULL, then the buffer to which it points is used to return the priority associated with the received message. - +.PP If the queue is empty, then, by default, .BR mq_receive () blocks until a message becomes available, @@ -83,7 +83,7 @@ If the flag is enabled for the message queue description, then the call instead fails immediately with the error .BR EAGAIN . - +.PP .BR mq_timedreceive () behaves just like .BR mq_receive (), diff --git a/man3/mq_send.3 b/man3/mq_send.3 index 58bd9afa18..c8693d5338 100644 --- a/man3/mq_send.3 +++ b/man3/mq_send.3 @@ -68,7 +68,7 @@ this length must be less than or equal to the queue's .I mq_msgsize attribute. Zero-length messages are allowed. - +.PP The .I msg_prio argument is a nonnegative integer that specifies the priority @@ -79,7 +79,7 @@ older messages with the same priority. See .BR mq_overview (7) for details on the range for the message priority. - +.PP If the message queue is already full (i.e., the number of messages on the queue equals the queue's .I mq_maxmsg @@ -92,7 +92,7 @@ If the flag is enabled for the message queue description, then the call instead fails immediately with the error .BR EAGAIN . - +.PP .BR mq_timedsend () behaves just like .BR mq_send (), diff --git a/man3/mtrace.3 b/man3/mtrace.3 index e9baa96f07..f957c09a9f 100644 --- a/man3/mtrace.3 +++ b/man3/mtrace.3 @@ -43,7 +43,7 @@ These hook functions record tracing information about memory allocation and deallocation. The tracing information can be used to discover memory leaks and attempts to free nonallocated memory in a program. - +.PP The .BR muntrace () function disables the hook functions installed by @@ -54,7 +54,7 @@ If no hook functions were successfully installed by .BR mtrace (), .BR muntrace () does nothing. - +.PP When .BR mtrace () is called, it checks the value of the environment variable @@ -62,7 +62,7 @@ is called, it checks the value of the environment variable which should contain the pathname of a file in which the tracing information is to be recorded. If the pathname is successfully opened, it is truncated to zero length. - +.PP If .BR MALLOC_TRACE is not set, @@ -105,7 +105,7 @@ In normal usage, is called once at the start of execution of a program, and .BR muntrace () is never called. - +.PP The tracing output produced after a call to .BR mtrace () is textual, but not designed to be human readable. @@ -115,7 +115,7 @@ that interprets the trace log and produces human-readable output. For best results, the traced program should be compiled with debugging enabled, so that line-number information is recorded in the executable. - +.PP The tracing performed by .BR mtrace () incurs a performance penalty (if @@ -176,7 +176,7 @@ Memory not freed: 0x084c9448 0x100 at /home/cecilia/t_mtrace.c:16 .fi .in - +.PP The first two messages about unfreed memory correspond to the two .BR malloc (3) calls inside the diff --git a/man3/newlocale.3 b/man3/newlocale.3 index 46e8d9dd82..5ee095a0d0 100644 --- a/man3/newlocale.3 +++ b/man3/newlocale.3 @@ -101,7 +101,7 @@ or is not .IR "(locale_t)\ 0" and is not a valid locale object handle, the behavior is undefined. - +.PP The .I category_mask argument is a bit mask that specifies the locale categories @@ -124,7 +124,7 @@ and Alternatively, the mask can be specified as .BR LC_ALL_MASK , which is equivalent to ORing all of the preceding constants. - +.PP For each category specified in .IR category_mask , the locale data from @@ -135,7 +135,7 @@ If a new locale object is being created, data for all categories not specified in .IR category_mask is taken from the default ("POSIX") locale. - +.PP The following preset values of .I locale are defined for all categories that can be specified in @@ -169,7 +169,7 @@ If is .BR LC_GLOBAL_LOCALE or is not valid locale object handle, the results are undefined. - +.PP Once a locale object has been freed, the program should make no further use of it. .SH RETURN VALUE @@ -229,7 +229,7 @@ The second command-line argument is optional; if it is present, it is used to set the .B LC_TIME category of the locale object. - +.PP Having created and initialized the locale object, the program then applies it using .BR uselocale (3), @@ -249,7 +249,7 @@ The format and language of the output will be affected by the setting. .PP The following shell sessions show some example runs of this program. - +.PP Set the .B LC_NUMERIC category to @@ -263,7 +263,7 @@ $ \fB./a.out fr_FR\fP Fri Mar 7 00:25:08 2014 .fi .in - +.PP Set the .B LC_NUMERIC category to @@ -282,7 +282,7 @@ $ \fB./a.out fr_FR it_IT\fP ven 07 mar 2014 00:26:01 CET .fi .in - +.PP Specify the .B LC_TIME setting as an empty string, diff --git a/man3/nextafter.3 b/man3/nextafter.3 index fd20e0dc5b..6aa768b9ca 100644 --- a/man3/nextafter.3 +++ b/man3/nextafter.3 @@ -76,14 +76,14 @@ is less than .IR x , these functions will return the largest representable number less than .IR x . - +.PP If .I x equals .IR y , the functions return .IR y . - +.PP The .BR nexttoward (), .BR nexttowardf (), @@ -100,7 +100,7 @@ these functions return the next representable floating-point value after .I x in the direction of .IR y . - +.PP If .I x equals @@ -110,14 +110,14 @@ then (cast to the same type as .IR x ) is returned. - +.PP If .I x or .I y is a NaN, a NaN is returned. - +.PP If .I x is finite, @@ -130,7 +130,7 @@ and the functions return or .BR HUGE_VALL , respectively, with the correct mathematical sign. - +.PP If .I x is not equal to diff --git a/man3/nextup.3 b/man3/nextup.3 index 701a957feb..e8c73bd80f 100644 --- a/man3/nextup.3 +++ b/man3/nextup.3 @@ -48,7 +48,7 @@ and .BR nextupl () functions return the next representable floating-point number greater than .IR x . - +.PP If .I x is the smallest representable negative number in the corresponding type, @@ -57,7 +57,7 @@ If .I x is 0, the returned value is the smallest representable positive number of the corresponding type. - +.PP If .I x is positive infinity, the returned value is positive infinity. @@ -66,12 +66,12 @@ If is negative infinity, the returned value is the largest representable finite negative number of the corresponding type. - +.PP If .I x is Nan, the returned value is NaN. - +.PP The value returned by .IR nextdown(x) is diff --git a/man3/nl_langinfo.3 b/man3/nl_langinfo.3 index d9330bd50f..b28dbbd3a1 100644 --- a/man3/nl_langinfo.3 +++ b/man3/nl_langinfo.3 @@ -133,7 +133,7 @@ On success, these functions return a pointer to a string which is the value corresponding to .I item in the specified locale. - +.PP If no locale has been selected by .BR setlocale (3) for the appropriate category, @@ -164,7 +164,7 @@ is freed or modified by .BR freelocale (3) or .BR newlocale (3). - +.PP POSIX specifies that the application may not modify the string returned by these functions. .SH ATTRIBUTES diff --git a/man3/ntp_gettime.3 b/man3/ntp_gettime.3 index 3a8a908276..19c8a1cd87 100644 --- a/man3/ntp_gettime.3 +++ b/man3/ntp_gettime.3 @@ -37,7 +37,7 @@ ntp_gettime, ntp_gettimex \- get time parameters (NTP daemon interface) Both of these APIs return information to the caller via the .I ntv argument, a structure of the following type: - +.PP .in +4n .nf struct ntptimeval { @@ -50,14 +50,14 @@ struct ntptimeval { }; .fi .in - +.PP The fields of this structure are as follows: .TP .I time The current time, expressed as a .I timeval structure: - +.IP .in +4n .nf struct timeval { @@ -142,7 +142,7 @@ is a GNU extension. .BR adjtimex (2) .BR ntp_adjtime (3), .BR time (7) - +.PP .ad l .UR http://www.slac.stanford.edu/comp/unix/\:package/\:rtems/\:src/\:ssrlApps/\:ntpNanoclock/\:api.htm NTP "Kernel Application Program Interface" diff --git a/man3/offsetof.3 b/man3/offsetof.3 index 0fcaf3af4e..f25ae3c830 100644 --- a/man3/offsetof.3 +++ b/man3/offsetof.3 @@ -41,14 +41,14 @@ returns the offset of the field .I member from the start of the structure .IR type . - +.PP This macro is useful because the sizes of the fields that compose a structure can vary across implementations, and compilers may insert different numbers of padding bytes between fields. Consequently, an element's offset is not necessarily given by the sum of the sizes of the previous elements. - +.PP A compiler error will result if .I member is not aligned to a byte boundary diff --git a/man3/on_exit.3 b/man3/on_exit.3 index 03392e4903..623bc42931 100644 --- a/man3/on_exit.3 +++ b/man3/on_exit.3 @@ -66,10 +66,10 @@ and the .I arg argument from .BR on_exit (). - +.PP The same function may be registered multiple times: it is called once for each registration. - +.PP When a child process is created via .BR fork (2), it inherits copies of its parent's registrations. @@ -93,7 +93,7 @@ T{ .BR on_exit () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO This function comes from SunOS 4, but is also present in glibc. It no longer occurs in Solaris (SunOS 5). diff --git a/man3/open_memstream.3 b/man3/open_memstream.3 index 27042ecf0b..b4d0249105 100644 --- a/man3/open_memstream.3 +++ b/man3/open_memstream.3 @@ -49,7 +49,7 @@ Initially, the buffer has a size of zero. After closing the stream, the caller should .BR free (3) this buffer. - +.PP The locations pointed to by .IR ptr and @@ -65,13 +65,13 @@ These values remain valid only as long as the caller performs no further output on the stream. If further output is performed, then the stream must again be flushed before trying to access these values. - +.PP A null byte is maintained at the end of the buffer. This byte is .I not included in the size value stored at .IR sizeloc . - +.PP The stream maintains the notion of a current position, which is initially zero (the start of the buffer). Each write operation implicitly adjusts the buffer position. @@ -82,7 +82,7 @@ or Moving the buffer position past the end of the data already written fills the intervening space with null characters. - +.PP The .BR open_wmemstream () is similar to @@ -118,7 +118,7 @@ T{ .BR open_wmemstream T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008. These functions are not specified in POSIX.1-2001, diff --git a/man3/opendir.3 b/man3/opendir.3 index cb199b010c..658c4b3d7c 100644 --- a/man3/opendir.3 +++ b/man3/opendir.3 @@ -66,7 +66,7 @@ The function opens a directory stream corresponding to the directory \fIname\fP, and returns a pointer to the directory stream. The stream is positioned at the first entry in the directory. - +.PP The .BR fdopendir () function @@ -136,10 +136,10 @@ is specified in POSIX.1-2008. .SH NOTES Filename entries can be read from a directory stream using .BR readdir (3). - +.PP The underlying file descriptor of the directory stream can be obtained using .BR dirfd (3). - +.PP The .BR opendir () function sets the close-on-exec flag for the file descriptor underlying the diff --git a/man3/openpty.3 b/man3/openpty.3 index db317aa361..90742ebca6 100644 --- a/man3/openpty.3 +++ b/man3/openpty.3 @@ -73,7 +73,7 @@ If .I winp is not NULL, the window size of the slave will be set to the values in .IR winp . - +.PP The .BR login_tty () function prepares for a login on the terminal @@ -88,7 +88,7 @@ the controlling terminal for the calling process, setting to be the standard input, output, and error streams of the current process, and closing .IR fd . - +.PP The .BR forkpty () function combines @@ -164,7 +164,7 @@ T{ .BR login_tty () T} Thread safety MT-Unsafe race:ttyname .TE - +.sp 1 .SH CONFORMING TO These are BSD functions, present in glibc. They are not standardized in POSIX. @@ -176,7 +176,7 @@ modifiers were added to the structure pointer arguments of and .BR forkpty () in glibc 2.8. - +.PP In versions of glibc before 2.0.92, .BR openpty () returns file descriptors for a BSD pseudoterminal pair; diff --git a/man3/perror.3 b/man3/perror.3 index ab383f444b..19bda76969 100644 --- a/man3/perror.3 +++ b/man3/perror.3 @@ -60,7 +60,7 @@ The .BR perror () function produces a message on standard error describing the last error encountered during a call to a system or library function. - +.PP First (if .I s is not NULL and @@ -71,10 +71,10 @@ is printed, followed by a colon and a blank. Then an error message corresponding to the current value of .I errno and a new-line. - +.PP To be of most use, the argument string should include the name of the function that incurred the error. - +.PP The global error list .IR sys_errlist "[]," which can be indexed by @@ -90,7 +90,7 @@ The use of is nowadays deprecated; use .BR strerror (3) instead - +.PP When a system call fails, it usually returns \-1 and sets the variable .I errno @@ -123,12 +123,12 @@ T{ .BR perror () T} Thread safety MT-Safe race:stderr .TE - +.sp 1 .SH CONFORMING TO .BR perror (), .IR errno : POSIX.1-2001, POSIX.1-2008, C89, C99, 4.3BSD. - +.PP The externals .I sys_nerr and diff --git a/man3/popen.3 b/man3/popen.3 index fc9524022d..3c8c51d0fc 100644 --- a/man3/popen.3 +++ b/man3/popen.3 @@ -81,7 +81,7 @@ This command is passed to using the .B \-c flag; interpretation, if any, is performed by the shell. - +.PP The .I type argument is a pointer to a null-terminated string which must contain @@ -132,7 +132,7 @@ or .BR pipe (2) calls fail, or if the function cannot allocate memory, NULL is returned. - +.PP .BR pclose (): on success, returns the exit status of the command; if .\" These conditions actually give undefined results, so I commented @@ -187,10 +187,10 @@ T{ .BR pclose () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. - +.PP The \(aqe\(aq value for .I type is a Linux extension. diff --git a/man3/posix_fallocate.3 b/man3/posix_fallocate.3 index ea1c3162e7..456b78312c 100644 --- a/man3/posix_fallocate.3 +++ b/man3/posix_fallocate.3 @@ -58,7 +58,7 @@ After a successful call to .BR posix_fallocate (), subsequent writes to bytes in the specified range are guaranteed not to fail because of lack of disk space. - +.PP If the size of the file is less than .IR offset + len , then the file is increased to this size; @@ -118,7 +118,7 @@ T} Thread safety MT-Safe (but see NOTES) .TE .SH CONFORMING TO POSIX.1-2001. - +.PP POSIX.1-2008 says that an implementation .I shall give the diff --git a/man3/posix_madvise.3 b/man3/posix_madvise.3 index 1629a02d66..255e2c659f 100644 --- a/man3/posix_madvise.3 +++ b/man3/posix_madvise.3 @@ -52,7 +52,7 @@ The system is free to use this advice in order to improve the performance of memory accesses (or to ignore the advice altogether), but calling .BR posix_madvise () shall not affect the semantics of access to memory in the specified range. - +.PP The .I advice argument is one of the following: @@ -113,7 +113,7 @@ is 0. On Linux, specifying .I len as 0 is permitted (as a successful no-op). - +.PP In glibc, this function is implemented using .BR madvise (2). However, since glibc 2.6, diff --git a/man3/posix_memalign.3 b/man3/posix_memalign.3 index f72077adf3..c8e382d57d 100644 --- a/man3/posix_memalign.3 +++ b/man3/posix_memalign.3 @@ -100,7 +100,7 @@ is either NULL, .\" glibc does this: or a unique pointer value that can later be successfully passed to .BR free (3). - +.PP The obsolete function .BR memalign () allocates @@ -111,7 +111,7 @@ The memory address will be a multiple of which must be a power of two. .\" The behavior of memalign() for size==0 is as for posix_memalign() .\" but no standards govern this. - +.PP The function .BR aligned_alloc () is the same as @@ -120,7 +120,7 @@ except for the added restriction that .I size should be a multiple of .IR alignment . - +.PP The obsolete function .BR valloc () allocates @@ -129,14 +129,14 @@ bytes and returns a pointer to the allocated memory. The memory address will be a multiple of the page size. It is equivalent to .IR "memalign(sysconf(_SC_PAGESIZE),size)" . - +.PP The obsolete function .BR pvalloc () is similar to .BR valloc (), but rounds the size of the allocation up to the next multiple of the system page size. - +.PP For all of these functions, the memory is not zeroed. .SH RETURN VALUE .BR aligned_alloc (), @@ -145,7 +145,7 @@ For all of these functions, the memory is not zeroed. and .BR pvalloc () return a pointer to the allocated memory, or NULL if the request fails. - +.PP .BR posix_memalign () returns zero on success, or one of the error values listed in the next section on failure. @@ -176,11 +176,11 @@ The functions and .BR pvalloc () have been available in all Linux libc libraries. - +.PP The function .BR aligned_alloc () was added to glibc in version 2.16. - +.PP The function .BR posix_memalign () is available since glibc 2.1.91. @@ -205,7 +205,7 @@ T{ .BR pvalloc () T} Thread safety MT-Unsafe init .TE - +.sp 1 .SH CONFORMING TO The function .BR valloc () @@ -213,19 +213,19 @@ appeared in 3.0BSD. It is documented as being obsolete in 4.3BSD, and as legacy in SUSv2. It does not appear in POSIX.1. - +.PP The function .BR pvalloc () is a GNU extension. - +.PP The function .BR memalign () appears in SunOS 4.1.3 but not in 4.4BSD. - +.PP The function .BR posix_memalign () comes from POSIX.1d and is specified in POSIX.1-2001 and POSIX.1-2008. - +.PP The function .BR aligned_alloc () is specified in the C11 standard. @@ -234,11 +234,11 @@ is specified in the C11 standard. Everybody agrees that .BR posix_memalign () is declared in \fI<stdlib.h>\fP. - +.PP On some systems .BR memalign () is declared in \fI<stdlib.h>\fP instead of \fI<malloc.h>\fP. - +.PP According to SUSv2, .BR valloc () is declared in \fI<stdlib.h>\fP. @@ -254,7 +254,7 @@ call that tells what alignment is needed. Now one can use .BR posix_memalign () to satisfy this requirement. - +.PP .BR posix_memalign () verifies that .I alignment @@ -263,7 +263,7 @@ matches the requirements detailed above. may not check that the .I alignment argument is correct. - +.PP POSIX requires that memory obtained from .BR posix_memalign () can be freed using @@ -291,7 +291,7 @@ The glibc implementation allows memory obtained from any of these functions to be reclaimed with .BR free (3). - +.PP The glibc .BR malloc (3) always returns 8-byte aligned memory addresses, so these functions are diff --git a/man3/posix_openpt.3 b/man3/posix_openpt.3 index d3cf74679a..a6e3a2b6be 100644 --- a/man3/posix_openpt.3 +++ b/man3/posix_openpt.3 @@ -47,7 +47,7 @@ The .BR posix_openpt () function opens an unused pseudoterminal master device, returning a file descriptor that can be used to refer to that device. - +.PP The .I flags argument is a bit mask that ORs together zero or more of @@ -88,7 +88,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. - +.PP .BR posix_openpt () is part of the UNIX 98 pseudoterminal support (see .BR pts (4)). diff --git a/man3/posix_spawn.3 b/man3/posix_spawn.3 index cc646b34aa..7e79a4a123 100644 --- a/man3/posix_spawn.3 +++ b/man3/posix_spawn.3 @@ -58,7 +58,7 @@ to support the .BR fork (2) system call. These machines are generally small, embedded systems lacking MMU support. - +.PP The .BR posix_spawn () and @@ -76,7 +76,7 @@ and system calls. In fact, they provide only a subset of the functionality that can be achieved by using the system calls. - +.PP The only difference between .BR posix_spawn () and @@ -99,7 +99,7 @@ For the remainder of this page, the discussion is phrased in terms of with the understanding that .BR posix_spawnp () differs only on the point just described. - +.PP The remaining arguments to these two functions are as follows: .IP * 3 The @@ -162,20 +162,20 @@ function commences by calling or possibly .BR vfork (2) (see below). - +.PP The PID of the new child process is placed in .IR *pid . The .BR posix_spawn () function then returns control to the parent process. - +.PP Subsequently, the parent can use one of the system calls described in .BR wait (2) to check the status of the child process. If the child fails in any of the housekeeping steps described below, or fails to execute the desired file, it exits with a status of 127. - +.PP The child process is created using .BR vfork (2) instead of @@ -210,7 +210,7 @@ is used if the caller requests it, or if there is no cleanup expected in the child before it .BR exec (3)s the requested file. - +.PP .SS pre-exec() step: housekeeping In between the .BR fork (2) @@ -256,7 +256,7 @@ will be affected as though the child was created with .BR fork (2) and it executed the program with .BR execve (2). - +.PP The process attributes actions are defined by the attributes object pointed to by .IR attrp . @@ -386,7 +386,7 @@ is NULL, then the default behaviors described above for each flag apply. .\" .I attrp .\" when you are done with it; .\" however, on Linux systems this operation is a no-op. - +.PP The .I file_actions argument specifies a sequence of file operations @@ -432,7 +432,7 @@ The requested operations are performed in the order they were added to .\" closed by the earlier operations .\" added to .\" .I file_actions . - +.PP If any of the housekeeping actions fails (due to bogus values being passed or other reasons why signal handling, process scheduling, process group ID functions, @@ -466,7 +466,7 @@ the contents of .IR *pid are unspecified, and these functions return an error number as described below. - +.PP Even when these functions return a success status, the child process may still fail for a plethora of reasons related to its pre-\fBexec\fR() initialization. @@ -526,7 +526,7 @@ only the POSIX-specified functions. (In other words, although these objects may be implemented as structures containing fields, portable programs must avoid dependence on such implementation details.) - +.PP According to POSIX, it unspecified whether fork handlers established with .BR pthread_atfork (3) are called when @@ -536,7 +536,7 @@ On glibc, .\" Tested on glibc 2.12 fork handlers are called only if the child is created using .BR fork (2). - +.PP There is no "posix_fspawn" function (i.e., a function that is to .BR posix_spawn () as @@ -570,7 +570,7 @@ The program accepts command-line attributes that can be used to create file actions and attributes objects. The remaining command-line arguments are used as the executable name and command-line arguments of the program that is executed in the child. - +.PP In the first run, the .BR date (1) command is executed in the child, and the diff --git a/man3/pow.3 b/man3/pow.3 index 5f26ef8b9a..119bb4e62a 100644 --- a/man3/pow.3 +++ b/man3/pow.3 @@ -73,7 +73,7 @@ On success, these functions return the value of .I x to the power of .IR y . - +.PP If .I x is a finite value less than 0, and @@ -81,7 +81,7 @@ is a finite value less than 0, and is a finite noninteger, a domain error occurs, .\" The domain error is generated at least as far back as glibc 2.4 and a NaN is returned. - +.PP If the result overflows, a range error occurs, .\" The range error is generated at least as far back as glibc 2.4 @@ -91,32 +91,32 @@ and the functions return or .BR HUGE_VALL , respectively, with the mathematically correct sign. - +.PP If result underflows, and is not representable, a range error occurs, and 0.0 is returned. .\" POSIX.1 does not specify the sign of the zero, .\" but http://sources.redhat.com/bugzilla/show_bug.cgi?id=2678 .\" points out that the zero has the wrong sign in some cases. - +.PP Except as specified below, if .I x or .I y is a NaN, the result is a NaN. - +.PP If .I x is +1, the result is 1.0 (even if .I y is a NaN). - +.PP If .I y is 0, the result is 1.0 (even if .I x is a NaN). - +.PP If .I x is +0 (\-0), @@ -124,7 +124,7 @@ and .I y is an odd integer greater than 0, the result is +0 (\-0). - +.PP If .I x is 0, @@ -132,7 +132,7 @@ and .I y greater than 0 and not an odd integer, the result is +0. - +.PP If .I x is \-1, @@ -140,7 +140,7 @@ and .I y is positive infinity or negative infinity, the result is 1.0. - +.PP If the absolute value of .I x is less than 1, @@ -148,7 +148,7 @@ and .I y is negative infinity, the result is positive infinity. - +.PP If the absolute value of .I x is greater than 1, @@ -156,7 +156,7 @@ and .I y is negative infinity, the result is +0. - +.PP If the absolute value of .I x is less than 1, @@ -164,7 +164,7 @@ and .I y is positive infinity, the result is +0. - +.PP If the absolute value of .I x is greater than 1, @@ -172,7 +172,7 @@ and .I y is positive infinity, the result is positive infinity. - +.PP If .I x is negative infinity, @@ -180,7 +180,7 @@ and .I y is an odd integer less than 0, the result is \-0. - +.PP If .I x is negative infinity, @@ -188,7 +188,7 @@ and .I y less than 0 and not an odd integer, the result is +0. - +.PP If .I x is negative infinity, @@ -196,7 +196,7 @@ and .I y is an odd integer greater than 0, the result is negative infinity. - +.PP If .I x is negative infinity, @@ -204,7 +204,7 @@ and .I y greater than 0 and not an odd integer, the result is positive infinity. - +.PP If .I x is positive infinity, @@ -212,7 +212,7 @@ and .I y less than 0, the result is +0. - +.PP If .I x is positive infinity, @@ -220,7 +220,7 @@ and .I y greater than 0, the result is positive infinity. - +.PP If .I x is +0 or \-0, @@ -235,7 +235,7 @@ or is returned, with the same sign as .IR x . - +.PP If .I x is +0 or \-0, @@ -325,7 +325,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to @@ -343,7 +343,7 @@ and not .BR powf () nor .BR powl (). - +.PP In glibc 2.9 and earlier, .\" .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6776 @@ -357,7 +357,7 @@ Since version 2.10, .\" or possibly 2.9, I haven't found the source code change .\" and I don't have a 2.9 system to test glibc does the right thing. - +.PP If .I x is negative, @@ -377,7 +377,7 @@ one sees this behavior when the absolute value of is greater than about 9.223373e18. .\" see bug http://sources.redhat.com/bugzilla/show_bug.cgi?id=3866 .\" and http://sources.redhat.com/bugzilla/show_bug.cgi?id=369 - +.PP In version 2.3.2 and earlier, .\" FIXME . Actually, 2.3.2 is the earliest test result I have; so yet .\" to confirm if this error occurs only in 2.3.2. diff --git a/man3/printf.3 b/man3/printf.3 index ad80df5ad6..d2779d6b62 100644 --- a/man3/printf.3 +++ b/man3/printf.3 @@ -112,7 +112,7 @@ and .BR vsnprintf () write to the character string .IR str . - +.PP The function .BR dprintf () is the same as @@ -122,7 +122,7 @@ except that it outputs to a file descriptor, instead of to a .I stdio stream. - +.PP The functions .BR snprintf () and @@ -131,7 +131,7 @@ write at most .I size bytes (including the terminating null byte (\(aq\e0\(aq)) to .IR str . - +.PP The functions .BR vprintf (), .BR vfprintf (), @@ -157,14 +157,14 @@ macro, the value of is undefined after the call. See .BR stdarg (3). - +.PP All of these functions write the output under the control of a .I format string that specifies how subsequent arguments (or arguments accessed via the variable-length argument facilities of .BR stdarg (3)) are converted for output. - +.PP C99 and POSIX.1-2001 specify that the results are undefined if a call to .BR sprintf (), .BR snprintf (), @@ -197,7 +197,7 @@ an optional .I precision and an optional .IR "length modifier" . - +.PP The arguments must correspond properly (after type promotion) with the conversion specifier. By default, the arguments are used in the order @@ -242,7 +242,7 @@ There may be no gaps in the numbers of arguments specified using \(aq$\(aq; for example, if arguments 1 and 3 are specified, argument 2 must also be specified somewhere in the format string. - +.PP For some numeric conversions a radix character ("decimal point") or thousands' grouping character is used. The actual character used @@ -603,7 +603,7 @@ and .BR Lf , .BR Lg , .BR LG ). - +.PP As a nonstandard extension, the GNU implementations treats .B ll and @@ -688,7 +688,7 @@ the precision specification. If the precision is missing, it is taken as 6; if the precision is explicitly zero, no decimal-point character appears. If a decimal point appears, at least one digit appears before it. - +.IP (SUSv2 does not know about .B F and says that character string representations for infinity and NaN @@ -784,7 +784,7 @@ are written. If a precision is given, no null byte need be present; if the precision is not specified, or is greater than the size of the array, the array must contain a terminating null byte. - +.IP If an .B l modifier is present: the @@ -858,7 +858,7 @@ specification is \(aq%%\(aq. .SH RETURN VALUE Upon successful return, these functions return the number of characters printed (excluding the null byte used to end output to strings). - +.PP The functions .BR snprintf () and @@ -874,7 +874,7 @@ Thus, a return value of .I size or more means that the output was truncated. (See also below under NOTES.) - +.PP If an output error is encountered, a negative value is returned. .SH ATTRIBUTES For an explanation of the terms used in this section, see @@ -898,7 +898,7 @@ T{ .BR vsnprintf () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO .BR fprintf (), .BR printf (), @@ -907,11 +907,11 @@ T} Thread safety MT-Safe locale .BR vfprintf (), .BR vsprintf (): POSIX.1-2001, POSIX.1-2008, C89, C99. - +.PP .BR snprintf (), .BR vsnprintf (): POSIX.1-2001, POSIX.1-2008, C99. - +.PP The .BR dprintf () and @@ -969,9 +969,9 @@ glibc 2.2 adds the conversion character \fBF\fP with C99 semantics, and the flag character \fBI\fP. .SH NOTES Some programs imprudently rely on code such as the following - +.PP sprintf(buf, "%s some further text", buf); - +.PP to append text to .IR buf . However, the standards explicitly note that the results are undefined @@ -987,7 +987,7 @@ Depending on the version of used, and the compiler options employed, calls such as the above will .B not produce the expected results. - +.PP The glibc implementation of the functions .BR snprintf () and diff --git a/man3/profil.3 b/man3/profil.3 index 2243ac1a3b..a553c007e4 100644 --- a/man3/profil.3 +++ b/man3/profil.3 @@ -87,7 +87,7 @@ T{ .BR profil () T} Thread safety MT-Unsafe .TE - +.sp 1 .SH CONFORMING TO Similar to a call in SVr4 (but not POSIX.1). .SH BUGS @@ -96,7 +96,7 @@ cannot be used on a program that also uses .B ITIMER_PROF interval timers (see .BR setitimer (2)). - +.PP True kernel profiling provides more accurate results. Libc 4.4 contained a kernel patch providing a system call profil. .SH SEE ALSO diff --git a/man3/program_invocation_name.3 b/man3/program_invocation_name.3 index 521f1c1902..127a49864d 100644 --- a/man3/program_invocation_name.3 +++ b/man3/program_invocation_name.3 @@ -43,14 +43,14 @@ in with the difference that the scope of .I program_invocation_name is global. - +.PP .I program_invocation_short_name contains the basename component of name that was used to invoke the calling program. That is, it is the same value as .IR program_invocation_name , with all text up to and including the final slash (/), if any, removed. - +.PP These variables are automatically initialized by the glibc run-time startup code. .SH CONFORMING TO diff --git a/man3/psignal.3 b/man3/psignal.3 index db2c43e33e..1f0b4a8907 100644 --- a/man3/psignal.3 +++ b/man3/psignal.3 @@ -68,7 +68,7 @@ describing the signal number \fIsig\fP, and a trailing newline. If the string \fIs\fP is NULL or empty, the colon and space are omitted. If \fIsig\fP is invalid, the message displayed will indicate an unknown signal. - +.PP The .BR psiginfo () function is like @@ -89,7 +89,7 @@ and the user ID and process ID of the sender, for signals set using .BR kill (2) or .BR sigqueue (3)). - +.PP The array \fIsys_siglist\fP holds the signal description strings indexed by signal number. .SH RETURN VALUE @@ -115,7 +115,7 @@ T{ .BR psiginfo () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008, 4.3BSD. .SH BUGS diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3 index ed0b85d7f5..973919f59d 100644 --- a/man3/pthread_atfork.3 +++ b/man3/pthread_atfork.3 @@ -43,7 +43,7 @@ function registers fork handlers that are to be executed when is called by this thread. The handlers are executed in the context of the thread that calls .BR fork (2). - +.PP Three kinds of handler can be registered: .IP * 3 .IR prepare @@ -65,7 +65,7 @@ Any of the three arguments may be NULL if no handler is needed in the corresponding phase of .BR fork (2) processing. - +.PP .SH RETURN VALUE On success, .BR pthread_atfork () @@ -107,7 +107,7 @@ was to provide a mechanism whereby the application (or a library) could ensure that mutexes and other process and thread state would be restored to a consistent state. In practice, this task is generally too difficult to be practicable. - +.PP After a .BR fork (2) in a multithreaded process returns in the child, @@ -116,7 +116,7 @@ the child should call only async-signal-safe functions (see until such time as it calls .BR execve (2) to execute a new program. - +.PP POSIX.1 specifies that .BR pthread_atfork () shall not fail with the error diff --git a/man3/pthread_attr_init.3 b/man3/pthread_attr_init.3 index 293617edc7..a9f920c6b7 100644 --- a/man3/pthread_attr_init.3 +++ b/man3/pthread_attr_init.3 @@ -47,19 +47,19 @@ using various related functions (listed under SEE ALSO), and then the object can be used in one or more .BR pthread_create (3) calls that create threads. - +.PP Calling .BR pthread_attr_init () on a thread attributes object that has already been initialized results in undefined behavior. - +.PP When a thread attributes object is no longer required, it should be destroyed using the .BR pthread_attr_destroy () function. Destroying a thread attributes object has no effect on threads that were created using that object. - +.PP Once a thread attributes object has been destroyed, it can be reinitialized using .BR pthread_attr_init (). @@ -108,7 +108,7 @@ Once created, the thread uses the .BR pthread_getattr_np (3) function (a nonstandard GNU extension) to retrieve the thread's attributes, and then displays those attributes. - +.PP If the program is run with no command-line argument, then it passes NULL as the .I attr @@ -117,7 +117,7 @@ argument of so that the thread is created with default attributes. Running the program on Linux/x86-32 with the NPTL threading implementation, we see the following: - +.PP .in +4n .nf .\" Results from glibc 2.8, SUSE 11.0; Oct 2008 @@ -135,7 +135,7 @@ Thread attributes: Stack size = 0x201000 bytes .fi .in - +.PP When we supply a stack size as a command-line argument, the program initializes a thread attributes object, sets various attributes in that object, @@ -143,7 +143,7 @@ and passes a pointer to the object in the call to .BR pthread_create (3). Running the program on Linux/x86-32 with the NPTL threading implementation, we see the following: - +.PP .in +4n .nf .\" Results from glibc 2.8, SUSE 11.0; Oct 2008 diff --git a/man3/pthread_attr_setaffinity_np.3 b/man3/pthread_attr_setaffinity_np.3 index a39e96efb4..c5405e0297 100644 --- a/man3/pthread_attr_setaffinity_np.3 +++ b/man3/pthread_attr_setaffinity_np.3 @@ -51,7 +51,7 @@ to the value specified in This attribute determines the CPU affinity mask of a thread created using the thread attributes object .IR attr . - +.PP The .BR pthread_attr_getaffinity_np () function @@ -60,14 +60,14 @@ referred to by .IR attr in the buffer pointed to by .IR cpuset . - +.PP The argument .I cpusetsize is the length (in bytes) of the buffer pointed to by .IR cpuset . Typically, this argument would be specified as .IR sizeof(cpu_set_t) . - +.PP For more details on CPU affinity masks, see .BR sched_setaffinity (2). For a description of a set of macros @@ -118,7 +118,7 @@ T{ .BR pthread_attr_getaffinity_np () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are nonstandard GNU extensions; hence the suffix "_np" (nonportable) in the names. diff --git a/man3/pthread_attr_setdetachstate.3 b/man3/pthread_attr_setdetachstate.3 index a31c662505..ea2fe0d56c 100644 --- a/man3/pthread_attr_setdetachstate.3 +++ b/man3/pthread_attr_setdetachstate.3 @@ -50,7 +50,7 @@ The detach state attribute determines whether a thread created using the thread attributes object .I attr will be created in a joinable or a detached state. - +.PP The following values may be specified in .IR detachstate : .TP @@ -67,7 +67,7 @@ will be created in a joinable state. The default setting of the detach state attribute in a newly initialized thread attributes object is .BR PTHREAD_CREATE_JOINABLE . - +.PP The .BR pthread_attr_getdetachstate () returns the detach state attribute of the thread attributes object @@ -103,7 +103,7 @@ POSIX.1-2001, POSIX.1-2008. See .BR pthread_create (3) for more details on detached and joinable threads. - +.PP A thread that is created in a joinable state should eventually either be joined using .BR pthread_join (3) @@ -111,7 +111,7 @@ or detached using .BR pthread_detach (3); see .BR pthread_create (3). - +.PP It is an error to specify the thread ID of a thread that was created in a detached state in a later call to diff --git a/man3/pthread_attr_setguardsize.3 b/man3/pthread_attr_setguardsize.3 index b6af3f2591..793eaf6e14 100644 --- a/man3/pthread_attr_setguardsize.3 +++ b/man3/pthread_attr_setguardsize.3 @@ -46,7 +46,7 @@ thread attributes object referred to by .I attr to the value specified in .IR guardsize . - +.PP If .I guardsize is greater than 0, @@ -56,15 +56,15 @@ the system allocates an additional region of at least .I guardsize bytes at the end of the thread's stack to act as the guard area for the stack (but see BUGS). - +.PP If .I guardsize is 0, then new threads created with .I attr will not have a guard area. - +.PP The default guard size is the same as the system page size. - +.PP If the stack address attribute has been set in .I attr (using @@ -79,7 +79,7 @@ it is the application's responsibility to handle stack overflow .BR mprotect (2) to manually define a guard area at the end of the stack that it has allocated). - +.PP The .BR pthread_attr_getguardsize () function returns the guard size attribute of the @@ -132,11 +132,11 @@ the system page size when creating a thread. .BR pthread_attr_getguardsize () returns the guard size that was set by .BR pthread_attr_setguardsize ().) - +.PP Setting a guard size of 0 may be useful to save memory in an application that creates many threads and knows that stack overflow can never occur. - +.PP Choosing a guard size larger than the default size may be necessary for detecting stack overflows if a thread allocates large data structures on the stack. @@ -151,7 +151,7 @@ error from .BR pthread_create (3) if the guard size value is too large, leaving no space for the actual stack.) - +.PP The obsolete LinuxThreads implementation did the right thing, allocating extra space at the end of the stack for the guard area. .\" glibc includes the guardsize within the allocated stack size, diff --git a/man3/pthread_attr_setinheritsched.3 b/man3/pthread_attr_setinheritsched.3 index 86a5af809d..914d56895d 100644 --- a/man3/pthread_attr_setinheritsched.3 +++ b/man3/pthread_attr_setinheritsched.3 @@ -52,7 +52,7 @@ the thread attributes object will inherit its scheduling attributes from the calling thread or whether it will take them from .IR attr . - +.PP The following scheduling attributes are affected by the inherit-scheduler attribute: scheduling policy @@ -61,7 +61,7 @@ scheduling priority .RB ( pthread_attr_setschedparam (3)), and contention scope .RB ( pthread_attr_setscope (3)). - +.PP The following values may be specified in .IR inheritsched : .TP @@ -83,7 +83,7 @@ by the attributes object. The default setting of the inherit-scheduler attribute in a newly initialized thread attributes object is .BR PTHREAD_INHERIT_SCHED . - +.PP The .BR pthread_attr_getinheritsched () returns the inherit-scheduler attribute of the thread attributes object diff --git a/man3/pthread_attr_setschedparam.3 b/man3/pthread_attr_setschedparam.3 index 394c32473d..7e4f110dbe 100644 --- a/man3/pthread_attr_setschedparam.3 +++ b/man3/pthread_attr_setschedparam.3 @@ -49,16 +49,16 @@ to the values specified in the buffer pointed to by These attributes determine the scheduling parameters of a thread created using the thread attributes object .IR attr . - +.PP The .BR pthread_attr_getschedparam () returns the scheduling parameter attributes of the thread attributes object .IR attr in the buffer pointed to by .IR param . - +.PP Scheduling parameters are maintained in the following structure: - +.PP .in +4n .nf struct sched_param { @@ -66,12 +66,12 @@ struct sched_param { }; .fi .in - +.PP As can be seen, only one scheduling parameter is supported. For details of the permitted ranges for scheduling priorities in each scheduling policy, see .BR sched (7). - +.PP In order for the parameter setting made by .BR pthread_attr_setschedparam () to have effect when calling diff --git a/man3/pthread_attr_setschedpolicy.3 b/man3/pthread_attr_setschedpolicy.3 index fda061d098..affc9c203b 100644 --- a/man3/pthread_attr_setschedpolicy.3 +++ b/man3/pthread_attr_setschedpolicy.3 @@ -49,7 +49,7 @@ to the value specified in This attribute determines the scheduling policy of a thread created using the thread attributes object .IR attr . - +.PP The supported values for .I policy are @@ -62,14 +62,14 @@ with the semantics described in .\" FIXME . pthread_setschedparam() places no restriction on the policy, .\" but pthread_attr_setschedpolicy() restricts policy to RR/FIFO/OTHER .\" http://sourceware.org/bugzilla/show_bug.cgi?id=7013 - +.PP The .BR pthread_attr_getschedpolicy () returns the scheduling policy attribute of the thread attributes object .IR attr in the buffer pointed to by .IR policy . - +.PP In order for the policy setting made by .BR pthread_attr_setschedpolicy () to have effect when calling diff --git a/man3/pthread_attr_setscope.3 b/man3/pthread_attr_setscope.3 index 4292145bbc..c778f42b7c 100644 --- a/man3/pthread_attr_setscope.3 +++ b/man3/pthread_attr_setscope.3 @@ -80,7 +80,7 @@ Linux supports .BR PTHREAD_SCOPE_SYSTEM , but not .BR PTHREAD_SCOPE_PROCESS . - +.PP On systems that support multiple contention scopes, then, in order for the parameter setting made by .BR pthread_attr_setscope () @@ -92,7 +92,7 @@ to set the inherit-scheduler attribute of the attributes object .I attr to .BR PTHREAD_EXPLICIT_SCHED . - +.PP The .BR pthread_attr_getscope () function returns the contention scope attribute of the @@ -139,7 +139,7 @@ bound directly to a single kernel-scheduling entity. This is the case on Linux for the obsolete LinuxThreads implementation and the modern NPTL implementation, which are both 1:1 threading implementations. - +.PP POSIX.1 specifies that the default contention scope is implementation-defined. .SH SEE ALSO diff --git a/man3/pthread_attr_setstack.3 b/man3/pthread_attr_setstack.3 index b980225a61..70a78b52b0 100644 --- a/man3/pthread_attr_setstack.3 +++ b/man3/pthread_attr_setstack.3 @@ -65,13 +65,13 @@ respectively. These attributes specify the location and size of the stack that should be used by a thread that is created using the thread attributes object .IR attr . - +.PP .I stackaddr should point to the lowest addressable byte of a buffer of .I stacksize bytes that was allocated by the caller. The pages of the allocated buffer should be both readable and writable. - +.PP The .BR pthread_attr_getstack () function returns the stack address and stack size attributes of the @@ -132,7 +132,7 @@ and the use of these functions should be avoided. (Use .BR pthread_attr_setstacksize (3) if an application simply requires a stack size other than the default.) - +.PP When an application employs .BR pthread_attr_setstack (), it takes over the responsibility of allocating the stack. @@ -143,7 +143,7 @@ If deemed necessary, it is the application's responsibility to allocate a guard area (one or more pages protected against reading and writing) to handle the possibility of stack overflow. - +.PP The address specified in .I stackaddr should be suitably aligned: @@ -154,7 +154,7 @@ may be useful for allocation. Probably, .IR stacksize should also be a multiple of the system page size. - +.PP If .I attr is used to create multiple threads, then the caller must change the diff --git a/man3/pthread_attr_setstackaddr.3 b/man3/pthread_attr_setstackaddr.3 index 40af17444d..e35c9cd565 100644 --- a/man3/pthread_attr_setstackaddr.3 +++ b/man3/pthread_attr_setstackaddr.3 @@ -46,7 +46,7 @@ Use and .BR pthread_attr_getstack (3) instead. - +.PP The .BR pthread_attr_setstackaddr () function sets the stack address attribute of the @@ -57,13 +57,13 @@ to the value specified in This attribute specifies the location of the stack that should be used by a thread that is created using the thread attributes object .IR attr . - +.PP .I stackaddr should point to a buffer of at least .B PTHREAD_STACK_MIN bytes that was allocated by the caller. The pages of the allocated buffer should be both readable and writable. - +.PP The .BR pthread_attr_getstackaddr () function returns the stack address attribute of the diff --git a/man3/pthread_attr_setstacksize.3 b/man3/pthread_attr_setstacksize.3 index d0f916e27e..7a7fe7adee 100644 --- a/man3/pthread_attr_setstacksize.3 +++ b/man3/pthread_attr_setstacksize.3 @@ -46,11 +46,11 @@ thread attributes object referred to by .I attr to the value specified in .IR stacksize . - +.PP The stack size attribute determines the minimum size (in bytes) that will be allocated for threads created using the thread attributes object .IR attr . - +.PP The .BR pthread_attr_getstacksize () function returns the stack size attribute of the @@ -98,10 +98,10 @@ POSIX.1-2001, POSIX.1-2008. .SH NOTES For details on the default stack size of new threads, see .BR pthread_create (3). - +.PP A thread's stack size is fixed at the time of thread creation. Only the main thread can dynamically grow its stack. - +.PP The .BR pthread_attr_setstack (3) function allows an application to set both the size and location diff --git a/man3/pthread_cancel.3 b/man3/pthread_cancel.3 index 8c9b206476..6cedc05058 100644 --- a/man3/pthread_cancel.3 +++ b/man3/pthread_cancel.3 @@ -46,7 +46,7 @@ its cancelability .I state and .IR type . - +.PP A thread's cancelability state, determined by .BR pthread_setcancelstate (3), can be @@ -58,7 +58,7 @@ then a cancellation request remains queued until the thread enables cancellation. If a thread has enabled cancellation, then its cancelability type determines when cancellation occurs. - +.PP A thread's cancellation type, determined by .BR pthread_setcanceltype (3), may be either @@ -74,7 +74,7 @@ the thread next calls a function that is a .IR "cancellation point" . A list of functions that are or may be cancellation points is provided in .BR pthreads (7). - +.PP When a cancellation requested is acted on, the following steps occur for .IR thread (in this order): @@ -134,7 +134,7 @@ T{ .BR pthread_cancel () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES @@ -151,7 +151,7 @@ The main thread joins with the canceled thread to check that its exit status was .BR PTHREAD_CANCELED . The following shell session shows what happens when we run the program: - +.PP .in +4n .nf $ ./a.out diff --git a/man3/pthread_cleanup_push.3 b/man3/pthread_cleanup_push.3 index 928615dbc9..2dc0b121ab 100644 --- a/man3/pthread_cleanup_push.3 +++ b/man3/pthread_cleanup_push.3 @@ -45,7 +45,7 @@ when a thread is canceled (or in various other circumstances described below); it might, for example, unlock a mutex so that it becomes available to other threads in the process. - +.PP The .BR pthread_cleanup_push () function pushes @@ -56,14 +56,14 @@ When is later invoked, it will be given .I arg as its argument. - +.PP The .BR pthread_cleanup_pop () function removes the routine at the top of the stack of clean-up handlers, and optionally executes it if .I execute is nonzero. - +.PP A cancellation clean-up handler is popped from the stack and executed in the following circumstances: .IP 1. 3 @@ -98,7 +98,7 @@ functions are paired within the same function, and at the same lexical nesting level. (In other words, a clean-up handler is established only during the execution of a specified section of code.) - +.PP Calling .BR longjmp (3) .RB ( siglongjmp (3)) @@ -137,7 +137,7 @@ T{ .BR pthread_cleanup_pop () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES @@ -151,7 +151,7 @@ implemented as macros that expand to text containing \(aq\fB{\fP\(aq and \(aq\fB}\fP\(aq, respectively. This means that variables declared within the scope of paired calls to these functions will be visible within only that scope. - +.PP POSIX.1 .\" The text was actually added in the 2004 TC2 says that the effect of using @@ -181,10 +181,10 @@ the main thread sends the other thread a cancellation request, or sets a global variable that causes the other thread to exit its loop and terminate normally (by doing a .IR return ). - +.PP In the following shell session, the main thread sends a cancellation request to the other thread: - +.PP .in +4n .nf $ \fB./a.out\fP @@ -196,16 +196,16 @@ Called clean-up handler Thread was canceled; cnt = 0 .fi .in - +.PP From the above, we see that the thread was canceled, and that the cancellation clean-up handler was called and it reset the value of the global variable .I cnt to 0. - +.PP In the next run, the main program sets a global variable that causes other thread to terminate normally: - +.PP .in +4n .nf $ \fB./a.out x\fP @@ -215,18 +215,18 @@ cnt = 1 Thread terminated normally; cnt = 2 .fi .in - +.PP From the above, we see that the clean-up handler was not executed (because .I cleanup_pop_arg was 0), and therefore the value of .I cnt was not reset. - +.PP In the next run, the main program sets a global variable that causes the other thread to terminate normally, and supplies a nonzero value for .IR cleanup_pop_arg : - +.PP .in +4n .nf $ \fB./a.out x 1\fP @@ -237,7 +237,7 @@ Called clean-up handler Thread terminated normally; cnt = 0 .fi .in - +.PP In the above, we see that although the thread was not canceled, the clean-up handler was executed, because the argument given to .BR pthread_cleanup_pop () diff --git a/man3/pthread_cleanup_push_defer_np.3 b/man3/pthread_cleanup_push_defer_np.3 index 4affcd41b5..64cac7b1b5 100644 --- a/man3/pthread_cleanup_push_defer_np.3 +++ b/man3/pthread_cleanup_push_defer_np.3 @@ -56,7 +56,7 @@ These functions are the same as and .BR pthread_cleanup_pop (3), except for the differences noted on this page. - +.PP Like .BR pthread_cleanup_push (3), .BR pthread_cleanup_push_defer_np () @@ -69,7 +69,7 @@ and sets the cancelability type to "deferred" (see this ensures that cancellation clean-up will occur even if the thread's cancelability type was "asynchronous" before the call. - +.PP Like .BR pthread_cleanup_pop (3), .BR pthread_cleanup_pop_restore_np () @@ -78,24 +78,24 @@ stack of cancellation clean-up handlers. In addition, it restores the thread's cancelability type to its value at the time of the matching .BR pthread_cleanup_push_defer_np (). - +.PP The caller must ensure that calls to these functions are paired within the same function, and at the same lexical nesting level. Other restrictions apply, as described in .BR pthread_cleanup_push (3). - +.PP This sequence of calls: - +.PP .in +4n .nf pthread_cleanup_push_defer_np(routine, arg); pthread_cleanup_pop_restore_np(execute); .fi .in - +.PP is equivalent to (but shorter and more efficient than): - +.PP .\" As far as I can see, LinuxThreads reverses the two substeps .\" in the push and pop below. .in +4n diff --git a/man3/pthread_create.3 b/man3/pthread_create.3 index 33099adb0c..3e2765a756 100644 --- a/man3/pthread_create.3 +++ b/man3/pthread_create.3 @@ -44,7 +44,7 @@ The new thread starts execution by invoking .IR arg is passed as the sole argument of .IR start_routine (). - +.PP The new thread terminates in one of the following ways: .IP * 2 It calls @@ -83,14 +83,14 @@ If .I attr is NULL, then the thread is created with default attributes. - +.PP Before returning, a successful call to .BR pthread_create () stores the ID of the new thread in the buffer pointed to by .IR thread ; this identifier is used to refer to the thread in subsequent calls to other pthreads functions. - +.PP The new thread inherits a copy of the creating thread's signal mask .RB ( pthread_sigmask (3)). The set of pending signals for the new thread is empty @@ -98,10 +98,10 @@ The set of pending signals for the new thread is empty The new thread does not inherit the creating thread's alternate signal stack .RB ( sigaltstack (2)). - +.PP The new thread inherits the calling thread's floating-point environment .RB ( fenv (3)). - +.PP The initial value of the new thread's CPU-time clock is 0 (see .BR pthread_getcpuclockid (3)). @@ -162,7 +162,7 @@ T{ .BR pthread_create () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES @@ -177,7 +177,7 @@ after a call to .BR pthread_create (), it is indeterminate which thread\(emthe caller or the new thread\(emwill next execute. - +.PP A thread may either be .I joinable or @@ -197,7 +197,7 @@ By default, a new thread is created in a joinable state, unless .I attr was set to create the thread in a detached state (using .BR pthread_attr_setdetachstate (3)). - +.PP .\" FIXME . Perhaps some of the following detail should be in .\" a future pthread_attr_setstacksize(3) page. On Linux/x86-32, the default stack size for a new thread is 2 megabytes. @@ -223,12 +223,12 @@ and is the source of many other nonconformances to the standard; see The program below demonstrates the use of .BR pthread_create (), as well as a number of other functions in the pthreads API. - +.PP In the following run, on a system providing the NPTL threading implementation, the stack size defaults to the value given by the "stack size" resource limit: - +.PP .in +4n .nf .RB "$" " ulimit \-s" @@ -242,11 +242,11 @@ Joined with thread 2; returned value was SALUT Joined with thread 3; returned value was SERVUS .fi .in - +.PP In the next run, the program explicitly sets a stack size of 1MB (using .BR pthread_attr_setstacksize (3)) for the created threads: - +.PP .in +4n .nf .RB "$" " ./a.out \-s 0x100000 hola salut servus" diff --git a/man3/pthread_detach.3 b/man3/pthread_detach.3 index 3509762f36..76c622f63a 100644 --- a/man3/pthread_detach.3 +++ b/man3/pthread_detach.3 @@ -43,7 +43,7 @@ as detached. When a detached thread terminates, its resources are automatically released back to the system without the need for another thread to join with the terminated thread. - +.PP Attempting to detach an already detached thread results in unspecified behavior. .SH RETURN VALUE @@ -73,28 +73,28 @@ T{ .BR pthread_detach () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES Once a thread has been detached, it can't be joined with .BR pthread_join (3) or be made joinable again. - +.PP A new thread can be created in a detached state using .BR pthread_attr_setdetachstate (3) to set the detached attribute of the .I attr argument of .BR pthread_create (3). - +.PP The detached attribute merely determines the behavior of the system when the thread terminates; it does not prevent the thread from being terminated if the process terminates using .BR exit (3) (or equivalently, if the main thread returns). - +.PP Either .BR pthread_join (3) or @@ -105,7 +105,7 @@ so that system resources for the thread can be released. process terminates.) .SH EXAMPLE The following statement detaches the calling thread: - +.PP pthread_detach(pthread_self()); .SH SEE ALSO .BR pthread_attr_setdetachstate (3), diff --git a/man3/pthread_exit.3 b/man3/pthread_exit.3 index 0d9c6ff9a9..fc83c5c17a 100644 --- a/man3/pthread_exit.3 +++ b/man3/pthread_exit.3 @@ -42,7 +42,7 @@ function terminates the calling thread and returns a value via that (if the thread is joinable) is available to another thread in the same process that calls .BR pthread_join (3). - +.PP Any clean-up handlers established by .BR pthread_cleanup_push (3) that have not yet been popped, @@ -52,14 +52,14 @@ If the thread has any thread-specific data, then, after the clean-up handlers have been executed, the corresponding destructor functions are called, in an unspecified order. - +.PP When a thread terminates, process-shared resources (e.g., mutexes, condition variables, semaphores, and file descriptors) are not released, and functions registered using .BR atexit (3) are not called. - +.PP After the last thread in a process terminates, the process terminates as by calling .BR exit (3) @@ -91,13 +91,13 @@ Performing a return from the start function of any thread other than the main thread results in an implicit call to .BR pthread_exit (), using the function's return value as the thread's exit status. - +.PP To allow other threads to continue execution, the main thread should terminate by calling .BR pthread_exit () rather than .BR exit (3). - +.PP The value pointed to by .IR retval should not be located on the calling thread's stack, diff --git a/man3/pthread_getattr_default_np.3 b/man3/pthread_getattr_default_np.3 index bfcd52d0dd..30375b24d6 100644 --- a/man3/pthread_getattr_default_np.3 +++ b/man3/pthread_getattr_default_np.3 @@ -102,7 +102,7 @@ The program below uses to fetch the default thread-creation attributes and then displays various settings from the returned thread attributes object. When running the program, we see the following output: - +.PP .in +4n .nf $ \fB./a.out\fP @@ -114,7 +114,7 @@ Detach state: JOINABLE Inherit scheduler: INHERIT .fi .in - +.PP .SS Program source \& .nf diff --git a/man3/pthread_getattr_np.3 b/man3/pthread_getattr_np.3 index 0b0224c8f4..8d07b46ee5 100644 --- a/man3/pthread_getattr_np.3 +++ b/man3/pthread_getattr_np.3 @@ -42,7 +42,7 @@ function initializes the thread attributes object referred to by .I attr so that it contains actual attribute values describing the running thread .IR thread . - +.PP The returned attribute values may differ from the corresponding attribute values passed in the .I attr @@ -65,7 +65,7 @@ Furthermore, if the stack address attribute was not set in the thread attributes object used to create the thread, then the returned thread attributes object will report the actual stack address that the implementation selected for the thread. - +.PP When the thread attributes object returned by .BR pthread_getattr_np () is no longer required, it should be destroyed using @@ -122,10 +122,10 @@ and stack size attributes. Command-line arguments can be used to set these attributes to values other than the default when creating the thread. The shell sessions below demonstrate the use of the program. - +.PP In the first run, on an x86-32 system, a thread is created using default attributes: - +.PP .in +4n .nf .RB "$" " ulimit \-s" " # No stack limit ==> default stack size is 2MB" @@ -137,11 +137,11 @@ Attributes of created thread: Stack size = 0x201000 (2101248) bytes .fi .in - +.PP In the following run, we see that if a guard size is specified, it is rounded up to the next multiple of the system page size (4096 bytes on x86-32): - +.PP .in +4n .nf .RB "$" " ./a.out \-g 4097" @@ -170,10 +170,10 @@ Attributes of created thread: .\" Stack size = 0x8000 (32768) bytes .\".fi .\".in - +.PP In the last run, the program manually allocates a stack for the thread. In this case, the guard size attribute is ignored. - +.PP .in +4n .nf .RB "$" " ./a.out \-g 4096 \-s 0x8000 \-a" diff --git a/man3/pthread_getcpuclockid.3 b/man3/pthread_getcpuclockid.3 index 73fbcea1fc..d027c01281 100644 --- a/man3/pthread_getcpuclockid.3 +++ b/man3/pthread_getcpuclockid.3 @@ -93,7 +93,7 @@ The program below creates a thread and then uses to retrieve the total process CPU time, and the per-thread CPU time consumed by the two threads. The following shell session shows an example run: - +.PP .in +4n .nf $ \fB./a.out\fP diff --git a/man3/pthread_join.3 b/man3/pthread_join.3 index eb8e315df3..31a0646809 100644 --- a/man3/pthread_join.3 +++ b/man3/pthread_join.3 @@ -46,7 +46,7 @@ returns immediately. The thread specified by .I thread must be joinable. - +.PP If .I retval is not NULL, then @@ -60,7 +60,7 @@ If the target thread was canceled, then .B PTHREAD_CANCELED is placed in the location pointed to by .IR retval . - +.PP If multiple threads simultaneously try to join with the same thread, the results are undefined. If the thread calling @@ -107,7 +107,7 @@ T{ .BR pthread_join () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES @@ -117,10 +117,10 @@ the caller is guaranteed that the target thread has terminated. The caller may then choose to do any clean-up that is required after termination of the thread (e.g., freeing memory or other resources that were allocated to the target thread). - +.PP Joining with a thread that has previously been joined results in undefined behavior. - +.PP Failure to join with a thread that is joinable (i.e., one that is not detached), produces a "zombie thread". @@ -128,13 +128,13 @@ Avoid doing this, since each zombie thread consumes some system resources, and when enough zombie threads have accumulated, it will no longer be possible to create new threads (or processes). - +.PP There is no pthreads analog of .IR "waitpid(-1,\ &status,\ 0)" , that is, "join with any terminated thread". If you believe you need this functionality, you probably need to rethink your application design. - +.PP All of the threads in a process are peers: any thread can join with any other thread in the process. .SH EXAMPLE diff --git a/man3/pthread_kill.3 b/man3/pthread_kill.3 index 1f1ae90679..8dcbfaba19 100644 --- a/man3/pthread_kill.3 +++ b/man3/pthread_kill.3 @@ -56,7 +56,7 @@ to a thread in the same process as the caller. The signal is asynchronously directed to .IR thread . - +.PP If .I sig is 0, then no signal is sent, but error checking is still performed. @@ -90,7 +90,7 @@ the handler will be invoked in the thread .IR thread , but if the disposition of the signal is "stop", "continue", or "terminate", this action will affect the whole process. - +.PP The glibc implementation of .BR pthread_kill () gives an error @@ -100,7 +100,7 @@ used internally by the NPTL threading implementation. See .BR nptl (7) for details. - +.PP POSIX.1-2008 recommends that if an implementation detects the use of a thread ID after the end of its lifetime, .BR pthread_kill () diff --git a/man3/pthread_kill_other_threads_np.3 b/man3/pthread_kill_other_threads_np.3 index d94a34cbe1..027908ebc6 100644 --- a/man3/pthread_kill_other_threads_np.3 +++ b/man3/pthread_kill_other_threads_np.3 @@ -68,7 +68,7 @@ This function is designed to address a limitation in the obsolete LinuxThreads implementation whereby the other threads of an application are not automatically terminated (as POSIX.1-2001 requires) during .BR execve (2). - +.PP In the NPTL threading implementation, .BR pthread_kill_other_threads_np () exists, but does nothing. diff --git a/man3/pthread_self.3 b/man3/pthread_self.3 index 1477fa76c5..ff36c7d4d7 100644 --- a/man3/pthread_self.3 +++ b/man3/pthread_self.3 @@ -72,15 +72,15 @@ can't portably be compared using the C equality operator (\fB==\fP); use .BR pthread_equal (3) instead. - +.PP Thread identifiers should be considered opaque: any attempt to use a thread ID other than in pthreads calls is nonportable and can lead to unspecified results. - +.PP Thread IDs are guaranteed to be unique only within a process. A thread ID may be reused after a terminated thread has been joined, or a detached thread has terminated. - +.PP The thread ID returned by .BR pthread_self () is not the same thing as the kernel thread ID returned by a call to diff --git a/man3/pthread_setaffinity_np.3 b/man3/pthread_setaffinity_np.3 index 64487719de..1180969e87 100644 --- a/man3/pthread_setaffinity_np.3 +++ b/man3/pthread_setaffinity_np.3 @@ -51,20 +51,20 @@ If the call is successful, and the thread is not currently running on one of the CPUs in .IR cpuset , then it is migrated to one of those CPUs. - +.PP The .BR pthread_getaffinity_np () function returns the CPU affinity mask of the thread .I thread in the buffer pointed to by .IR cpuset . - +.PP For more details on CPU affinity masks, see .BR sched_setaffinity (2). For a description of a set of macros that can be used to manipulate and inspect CPU sets, see .BR CPU_SET (3). - +.PP The argument .I cpusetsize is the length (in bytes) of the buffer pointed to by @@ -143,20 +143,20 @@ runs if the "cpuset" mechanism described in is being used. These restrictions on the actual set of CPUs on which the thread will run are silently imposed by the kernel. - +.PP These functions are implemented on top of the .BR sched_setaffinity (2) and .BR sched_getaffinity (2) system calls. - +.PP In glibc 2.3.3 only, versions of these functions were provided that did not have a .I cpusetsize argument. Instead the CPU set size given to the underlying system calls was always .IR sizeof(cpu_set_t) . - +.PP A new thread created by .BR pthread_create (3) inherits a copy of its creator's CPU affinity mask. @@ -168,7 +168,7 @@ to set its CPU affinity mask to include CPUs 0 to 7 and then calls .BR pthread_getaffinity_np () to check the resulting CPU affinity mask of the thread. - +.PP .nf #define _GNU_SOURCE #include <pthread.h> diff --git a/man3/pthread_setcancelstate.3 b/man3/pthread_setcancelstate.3 index 5b1d379b4e..e5d4226311 100644 --- a/man3/pthread_setcancelstate.3 +++ b/man3/pthread_setcancelstate.3 @@ -139,7 +139,7 @@ POSIX.1-2001, POSIX.1-2008. .SH NOTES For details of what happens when a thread is canceled, see .BR pthread_cancel (3). - +.PP Briefly disabling cancelability is useful if a thread performs some critical action that must not be interrupted by a cancellation request. @@ -165,7 +165,7 @@ Furthermore, some internal data structures family of functions) may be left in an inconsistent state if cancellation occurs in the middle of the function call. Consequently, clean-up handlers cease to be useful. - +.PP Functions that can be safely asynchronously canceled are called .IR "async-cancel-safe functions" . POSIX.1-2001 and POSIX.1-2008 require only that @@ -176,7 +176,7 @@ and be async-cancel-safe. In general, other library functions can't be safely called from an asynchronously cancelable thread. - +.PP One of the few circumstances in which asynchronous cancelability is useful is for cancellation of a thread that is in a pure compute-bound loop. .SS Portability notes diff --git a/man3/pthread_setconcurrency.3 b/man3/pthread_setconcurrency.3 index 173632588b..eafa335dd5 100644 --- a/man3/pthread_setconcurrency.3 +++ b/man3/pthread_setconcurrency.3 @@ -45,12 +45,12 @@ The implementation takes this only as a hint: POSIX.1 does not specify the level of concurrency that should be provided as a result of calling .BR pthread_setconcurrency (). - +.PP Specifying .I new_level as 0 instructs the implementation to manage the concurrency level as it deems appropriate. - +.PP .BR pthread_getconcurrency () returns the current value of the concurrency level for this process. .SH RETURN VALUE @@ -58,7 +58,7 @@ On success, .BR pthread_setconcurrency () returns 0; on error, it returns a nonzero error number. - +.PP .BR pthread_getconcurrency () always succeeds, returning the concurrency level set by a previous call to .BR pthread_setconcurrency (), @@ -97,14 +97,14 @@ T} Thread safety MT-Safe POSIX.1-2001, POSIX.1-2008. .SH NOTES The default concurrency level is 0. - +.PP Concurrency levels are meaningful only for M:N threading implementations, where at any moment a subset of a process's set of user-level threads may be bound to a smaller number of kernel-scheduling entities. Setting the concurrency level allows the application to give the system a hint as to the number of kernel-scheduling entities that should be provided for efficient execution of the application. - +.PP Both LinuxThreads and NPTL are 1:1 threading implementations, so setting the concurrency level has no meaning. In other words, diff --git a/man3/pthread_setname_np.3 b/man3/pthread_setname_np.3 index 9170fb1c6f..1747344846 100644 --- a/man3/pthread_setname_np.3 +++ b/man3/pthread_setname_np.3 @@ -52,7 +52,7 @@ The argument specifies the thread whose name is to be changed; .I name specifies the new name. - +.PP The .BR pthread_getname_np () function can be used to retrieve the name of the thread. @@ -112,7 +112,7 @@ T{ .BR pthread_getname_np () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are nonstandard GNU extensions. .SH NOTES @@ -131,7 +131,7 @@ The program below demonstrates the use of .BR pthread_setname_np () and .BR pthread_getname_np (). - +.PP The following shell session shows a sample run of the program: .in +4n .nf diff --git a/man3/pthread_setschedparam.3 b/man3/pthread_setschedparam.3 index 08cf3f790e..92f0cd2103 100644 --- a/man3/pthread_setschedparam.3 +++ b/man3/pthread_setschedparam.3 @@ -43,7 +43,7 @@ The .BR pthread_setschedparam () function sets the scheduling policy and parameters of the thread .IR thread . - +.PP .I policy specifies the new scheduling policy for .IR thread . @@ -54,13 +54,13 @@ and their semantics, are described in .\" FIXME . pthread_setschedparam() places no restriction on the policy, .\" but pthread_attr_setschedpolicy() restricts policy to RR/FIFO/OTHER .\" http://sourceware.org/bugzilla/show_bug.cgi?id=7013 - +.PP The structure pointed to by .I param specifies the new scheduling parameters for .IR thread . Scheduling parameters are maintained in the following structure: - +.PP .in +4n .nf struct sched_param { @@ -68,12 +68,12 @@ struct sched_param { }; .fi .in - +.PP As can be seen, only one scheduling parameter is supported. For details of the permitted ranges for scheduling priorities in each scheduling policy, see .BR sched (7). - +.PP The .BR pthread_getschedparam () function returns the scheduling policy and parameters of the thread @@ -166,7 +166,7 @@ and .BR pthread_getschedparam (), as well as the use of a number of other scheduling-related pthreads functions. - +.PP In the following run, the main thread sets its scheduling policy to .BR SCHED_FIFO with a priority of 10, @@ -199,17 +199,17 @@ Scheduler attributes of new thread policy=SCHED_RR, priority=20 .fi .in - +.PP In the above output, one can see that the scheduling policy and priority were taken from the values specified in the thread attributes object. - +.PP The next run is the same as the previous, except that the inherit scheduler attribute is set to .BR PTHREAD_INHERIT_SCHED , meaning that threads created using the thread attributes object should ignore the scheduling attributes specified in the attributes object and instead take their scheduling attributes from the creating thread. - +.PP .in +4n .nf # \fB./a.out \-mf10 \-ar20 \-i i\fP @@ -224,11 +224,11 @@ Scheduler attributes of new thread policy=SCHED_FIFO, priority=10 .fi .in - +.PP In the above output, one can see that the scheduling policy and priority were taken from the creating thread, rather than the thread attributes object. - +.PP Note that if we had omitted the .IR "\-i\ i" option, the output would have been the same, since diff --git a/man3/pthread_sigmask.3 b/man3/pthread_sigmask.3 index e528448e56..aa9afe5503 100644 --- a/man3/pthread_sigmask.3 +++ b/man3/pthread_sigmask.3 @@ -55,7 +55,7 @@ function is just like with the difference that its use in multithreaded programs is explicitly specified by POSIX.1. Other differences are noted in this page. - +.PP For a description of the arguments and operation of this function, see .BR sigprocmask (2). .SH RETURN VALUE @@ -82,7 +82,7 @@ T} Thread safety MT-Safe POSIX.1-2001, POSIX.1-2008. .SH NOTES A new thread inherits a copy of its creator's signal mask. - +.PP The glibc .BR pthread_sigmask () function silently ignores attempts to block the two real-time signals that @@ -95,7 +95,7 @@ The program below blocks some signals in the main thread, and then creates a dedicated thread to fetch those signals via .BR sigwait (3). The following shell session demonstrates its use: - +.PP .in +4n .nf .RB "$" " ./a.out &" diff --git a/man3/pthread_sigqueue.3 b/man3/pthread_sigqueue.3 index a123a23a09..458fec5dd4 100644 --- a/man3/pthread_sigqueue.3 +++ b/man3/pthread_sigqueue.3 @@ -51,7 +51,7 @@ function performs a similar task to but, rather than sending a signal to a process, it sends a signal to a thread in the same process as the calling thread. - +.PP The .I thread argument is the ID of a thread in the same process as the caller. diff --git a/man3/pthread_testcancel.3 b/man3/pthread_testcancel.3 index 7e5a366309..7ae467ed53 100644 --- a/man3/pthread_testcancel.3 +++ b/man3/pthread_testcancel.3 @@ -40,7 +40,7 @@ Calling creates a cancellation point within the calling thread, so that a thread that is otherwise executing code that contains no cancellation points will respond to a cancellation request. - +.PP If cancelability is disabled (using .BR pthread_setcancelstate (3)), or no cancellation request is pending, diff --git a/man3/pthread_tryjoin_np.3 b/man3/pthread_tryjoin_np.3 index 01bcb429d8..df04e7e27d 100644 --- a/man3/pthread_tryjoin_np.3 +++ b/man3/pthread_tryjoin_np.3 @@ -43,7 +43,7 @@ Compile and link with \fI\-pthread\fP. These functions operate in the same way as .BR pthread_join (3), except for the differences described on this page. - +.PP The .BR pthread_tryjoin_np () function performs a nonblocking join with the thread @@ -55,7 +55,7 @@ If has not yet terminated, then instead of blocking, as is done by .BR pthread_join (3), the call returns an error. - +.PP The .BR pthread_timedjoin_np () function performs a join-with-timeout. @@ -73,7 +73,7 @@ The argument is a structure of the following form, specifying an absolute time measured since the Epoch (see .BR time (2)): - +.PP .in +4n .nf struct timespec { @@ -137,7 +137,7 @@ These functions are nonstandard GNU extensions; hence the suffix "_np" (nonportable) in the names. .SH EXAMPLE The following code waits to join for up to 5 seconds: - +.PP .nf struct timespec ts; int s; diff --git a/man3/ptsname.3 b/man3/ptsname.3 index b9b082add2..bbcb6e1d05 100644 --- a/man3/ptsname.3 +++ b/man3/ptsname.3 @@ -40,7 +40,7 @@ The function returns the name of the slave pseudoterminal device corresponding to the master referred to by .IR fd . - +.PP The .BR ptsname_r () function is the reentrant equivalent of @@ -59,7 +59,7 @@ returns a pointer to a string in static storage which will be overwritten by subsequent calls. This pointer must not be freed. On failure, NULL is returned. - +.PP On success, .BR ptsname_r () returns 0. @@ -110,11 +110,11 @@ T} Thread safety MT-Safe .SH CONFORMING TO .BR ptsname (): POSIX.1-2001, POSIX.1-2008. - +.PP .BR ptsname () is part of the UNIX 98 pseudoterminal support (see .BR pts (4)). - +.PP .BR ptsname_r () is a Linux extension, that is proposed for inclusion .\" FIXME . for later review when Issue 8 is one day released diff --git a/man3/putgrent.3 b/man3/putgrent.3 index 64de0d404b..15b74cf14d 100644 --- a/man3/putgrent.3 +++ b/man3/putgrent.3 @@ -52,7 +52,7 @@ T{ .BR putgrent () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO This function is a GNU extension. .SH SEE ALSO diff --git a/man3/putpwent.3 b/man3/putpwent.3 index e733ee9275..ed9c5256a9 100644 --- a/man3/putpwent.3 +++ b/man3/putpwent.3 @@ -94,7 +94,7 @@ T{ .BR putpwent () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO SVr4. .SH SEE ALSO diff --git a/man3/qsort.3 b/man3/qsort.3 index 6a1d38a8ce..e6efbfea2a 100644 --- a/man3/qsort.3 +++ b/man3/qsort.3 @@ -110,7 +110,7 @@ T{ .BR qsort_r () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO .BR qsort (): POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. @@ -121,7 +121,7 @@ as shown in the example below. .SH EXAMPLE For one example of use, see the example under .BR bsearch (3). - +.PP Another example is the following program, which sorts the strings given in its command-line arguments: .sp diff --git a/man3/random.3 b/man3/random.3 index 48ea1d3c1f..dd6f859854 100644 --- a/man3/random.3 +++ b/man3/random.3 @@ -129,14 +129,14 @@ function returns a value between 0 and The .BR srandom () function returns no value. - +.PP The .BR initstate () function returns a pointer to the previous state array. On error, .I errno is set to indicate the cause. - +.PP On success, .BR setstate () returns a pointer to the previous state array. diff --git a/man3/random_r.3 b/man3/random_r.3 index 1f246a8611..f1b43c6665 100644 --- a/man3/random_r.3 +++ b/man3/random_r.3 @@ -62,7 +62,7 @@ of the functions described in .BR random (3). They are suitable for use in multithreaded programs where each thread needs to obtain an independent, reproducible sequence of random numbers. - +.PP The .BR random_r () function is like @@ -75,7 +75,7 @@ which must have been previously initialized by .BR initstate_r (). The generated random number is returned in the argument .IR result . - +.PP The .BR srandom_r () function is like @@ -86,7 +86,7 @@ whose state is maintained in the object pointed to by which must have been previously initialized by .BR initstate_r (), instead of the seed associated with the global state variable. - +.PP The .BR initstate_r () function is like @@ -114,7 +114,7 @@ should typically be allocated as a static variable, or allocated on the heap using .BR malloc (3) or similar.) - +.PP The .BR setstate_r () function is like diff --git a/man3/rcmd.3 b/man3/rcmd.3 index 555a97e125..ac688a6cbc 100644 --- a/man3/rcmd.3 +++ b/man3/rcmd.3 @@ -258,7 +258,7 @@ set according to the reason for failure. The error code .BR EAGAIN is overloaded to mean "All network ports in use." - +.PP For information on the return from .BR ruserok () and @@ -296,7 +296,7 @@ T{ .BR ruserok_af () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO Not in POSIX.1. Present on the BSDs, Solaris, and many other systems. diff --git a/man3/re_comp.3 b/man3/re_comp.3 index 92a2964f37..64c2f58cfd 100644 --- a/man3/re_comp.3 +++ b/man3/re_comp.3 @@ -49,7 +49,7 @@ If is NULL, no operation is performed and the pattern buffer's contents are not altered. - +.PP .BR re_exec () is used to assess whether the null-terminated string pointed to by .I string @@ -60,7 +60,7 @@ matches the previously compiled returns NULL on successful compilation of .I regex otherwise it returns a pointer to an appropriate error message. - +.PP .BR re_exec () returns 1 for a successful match, zero for failure. .SH ATTRIBUTES diff --git a/man3/readdir.3 b/man3/readdir.3 index 4956618b38..92279f1498 100644 --- a/man3/readdir.3 +++ b/man3/readdir.3 @@ -76,7 +76,7 @@ and .IR d_ino . The other fields are unstandardized, and not present on all systems; see NOTES below for some further details. - +.PP The fields of the .I dirent structure are as follows: @@ -170,7 +170,7 @@ structure. (This structure may be statically allocated; do not attempt to .BR free (3) it.) - +.PP If the end of the directory stream is reached, NULL is returned and .I errno is not changed. @@ -200,7 +200,7 @@ T{ .BR readdir () T} Thread safety MT-Unsafe race:dirstream .TE - +.sp 1 .PP In the current POSIX.1 specification (POSIX.1-2008), .BR readdir () @@ -226,12 +226,12 @@ POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD. .SH NOTES A directory stream is opened using .BR opendir (3). - +.PP The order in which filenames are read by successive calls to .BR readdir () depends on the filesystem implementation; it is unlikely that the names will be sorted in any fashion. - +.PP Only the fields .I d_name and (as an XSI extension) @@ -259,7 +259,7 @@ structure definition shown above is taken from the glibc headers, and shows the .I d_name field with a fixed size. - +.PP .IR Warning : applications should avoid any dependence on the size of the .I d_name @@ -269,7 +269,7 @@ POSIX defines it as a character array of unspecified size, with at most .B NAME_MAX characters preceding the terminating null byte (\(aq\\0\(aq). - +.PP POSIX.1 explicitly notes that this field should not be used as an lvalue. The standard also notes that the use of .I sizeof(d_name) @@ -283,11 +283,11 @@ By implication, the use to capture the size of the record including the size of .IR d_name is also incorrect. - +.PP Note that while the call - +.PP fpathconf(fd, _PC_NAME_MAX) - +.PP returns the value 255 for most filesystems, on some filesystems (e.g., CIFS, Windows SMB servers), the null-terminated filename that is (correctly) returned in diff --git a/man3/realpath.3 b/man3/realpath.3 index 567a438efd..e4985009d4 100644 --- a/man3/realpath.3 +++ b/man3/realpath.3 @@ -70,7 +70,7 @@ The resulting path will have no symbolic link, or .I "/../" components. - +.PP If .I resolved_path is specified as NULL, then @@ -95,7 +95,7 @@ If there is no error, .BR realpath () returns a pointer to the .IR resolved_path . - +.PP Otherwise, it returns NULL, the contents of the array .I resolved_path @@ -151,7 +151,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO 4.4BSD, POSIX.1-2001. - +.PP POSIX.1-2001 says that the behavior if .I resolved_path is NULL is implementation-defined. diff --git a/man3/recno.3 b/man3/recno.3 index e5de9a3138..fa44aa786f 100644 --- a/man3/recno.3 +++ b/man3/recno.3 @@ -51,7 +51,7 @@ Since version 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. - +.PP The routine .BR dbopen (3) is the library interface to database files. @@ -226,7 +226,7 @@ Only big and little endian byte order is supported. .BR dbopen (3), .BR hash (3), .BR mpool (3) - +.PP .IR "Document Processing in a Relational Database System" , Michael Stonebraker, Heidi Stettner, Joseph Kalash, Antonin Guttman, Nadene Lynn, Memorandum No. UCB/ERL M82/32, May 1982. diff --git a/man3/regex.3 b/man3/regex.3 index 68aab89a84..9ca0d79e45 100644 --- a/man3/regex.3 +++ b/man3/regex.3 @@ -53,7 +53,7 @@ is used to compile a regular expression into a form that is suitable for subsequent .BR regexec () searches. - +.PP .BR regcomp () is supplied with .IR preg , @@ -62,14 +62,14 @@ a pointer to a pattern buffer storage area; a pointer to the null-terminated string and .IR cflags , flags used to determine the type of compilation. - +.PP All regular expression searching must be done via a compiled pattern buffer, thus .BR regexec () must always be supplied with the address of a .BR regcomp () initialized pattern buffer. - +.PP .I cflags may be the .RB bitwise- or @@ -102,11 +102,11 @@ are ignored if the pattern buffer supplied was compiled with this flag set. .TP .B REG_NEWLINE Match-any-character operators don't match a newline. - +.IP A nonmatching list .RB ( [^...] ) not containing a newline does not match a newline. - +.IP Match-beginning-of-line operator .RB ( ^ ) matches the empty string immediately after a newline, regardless of @@ -116,7 +116,7 @@ the execution flags of .BR regexec (), contains .BR REG_NOTBOL . - +.IP Match-end-of-line operator .RB ( $ ) matches the empty string immediately before a newline, regardless of @@ -182,14 +182,14 @@ subexpression matches, must be at least .IR N+1 .) Any unused structure elements will contain the value \-1. - +.PP The .I regmatch_t structure which is the type of .I pmatch is defined in .IR <regex.h> . - +.PP .in +4n .nf typedef struct { @@ -198,7 +198,7 @@ typedef struct { } regmatch_t; .fi .in - +.PP Each .I rm_so element that is not \-1 indicates the start offset of the next largest @@ -214,7 +214,7 @@ is used to turn the error codes that can be returned by both and .BR regexec () into error message strings. - +.PP .BR regerror () is passed the error code, .IR errcode , @@ -247,7 +247,7 @@ process, .SH RETURN VALUE .BR regcomp () returns zero for a successful compilation or an error code for failure. - +.PP .BR regexec () returns zero for a successful match or .B REG_NOMATCH diff --git a/man3/remainder.3 b/man3/remainder.3 index 43461c3180..7527fe5bc9 100644 --- a/man3/remainder.3 +++ b/man3/remainder.3 @@ -104,7 +104,7 @@ If the absolute value of is 0.5, .I n is chosen to be even. - +.PP These functions are unaffected by the current rounding mode (see .BR fenv (3)). .LP @@ -117,13 +117,13 @@ functions return the floating-point remainder, \fIx\fP\-\fIn\fP*\fIy\fP. If the return value is 0, it has the sign of .IR x . - +.PP If .I x or .I y is a NaN, a NaN is returned. - +.PP If .I x is an infinity, @@ -132,7 +132,7 @@ and is not a NaN, a domain error occurs, and a NaN is returned. - +.PP If .I y is zero, @@ -198,7 +198,7 @@ The functions and .BR remainderl () are specified in C99, POSIX.1-2001, and POSIX.1-2008. - +.PP The function .BR drem () is from 4.3BSD. @@ -218,12 +218,12 @@ etc. Before glibc 2.15, .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6779 the call - +.PP remainder(nan(""), 0); - +.PP returned a NaN, as expected, but wrongly caused a domain error. Since glibc 2.15, a silent NaN (i.e., no domain error) is returned. - +.PP Before glibc 2.15, .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6783 .I errno diff --git a/man3/remove.3 b/man3/remove.3 index 183205b858..dfd9258284 100644 --- a/man3/remove.3 +++ b/man3/remove.3 @@ -43,18 +43,18 @@ It calls for files, and .BR rmdir (2) for directories. - +.PP If the removed name was the last link to a file and no processes have the file open, the file is deleted and the space it was using is made available for reuse. - +.PP If the name was the last link to a file, but any processes still have the file open, the file will remain in existence until the last file descriptor referring to it is closed. - +.PP If the name referred to a symbolic link, the link is removed. - +.PP If the name referred to a socket, FIFO, or device, the name is removed, but processes which have the object open may continue to use it. .SH RETURN VALUE diff --git a/man3/remquo.3 b/man3/remquo.3 index 91ec8459eb..9d7e374bce 100644 --- a/man3/remquo.3 +++ b/man3/remquo.3 @@ -48,17 +48,17 @@ A few bits of the quotient are stored via the .I quo pointer. The remainder is returned as the function result. - +.PP The value of the remainder is the same as that computed by the .BR remainder (3) function. - +.PP The value stored via the .I quo pointer has the sign of .IR "x\ /\ y" and agrees with the quotient in at least the low order 3 bits. - +.PP For example, \fIremquo(29.0,\ 3.0)\fP returns \-1.0 and might store 2. Note that the actual quotient might not fit in an integer. .\" A possible application of this function might be the computation @@ -70,13 +70,13 @@ Note that the actual quotient might not fit in an integer. On success, these functions return the same value as the analogous functions described in .BR remainder (3). - +.PP If .I x or .I y is a NaN, a NaN is returned. - +.PP If .I x is an infinity, @@ -85,7 +85,7 @@ and is not a NaN, a domain error occurs, and a NaN is returned. - +.PP If .I y is zero, diff --git a/man3/resolver.3 b/man3/resolver.3 index b23bf5b323..f11412036e 100644 --- a/man3/resolver.3 +++ b/man3/resolver.3 @@ -109,10 +109,10 @@ Link with \fI\-lresolv\fP. .B Note: This page is incomplete (various resolver functions provided by glibc are not described) and likely out of date. - +.PP The functions described below make queries to and interpret the responses from Internet domain name servers. - +.PP The API consists of a set of more modern, reentrant functions and an older set of nonreentrant functions that have been superseded. The traditional resolver interfaces such as @@ -128,7 +128,7 @@ BIND 8.2 introduced a set of new interfaces and so on, which take a .I res_state as their first argument, so you can use a per-thread resolver state. - +.PP The .BR res_ninit () and @@ -146,7 +146,7 @@ or .BR res_init () is normally executed by the first call to one of the other functions. - +.PP The .BR res_nquery () and @@ -156,7 +156,7 @@ fully qualified domain name \fIname\fP of specified \fItype\fP and \fIclass\fP. The reply is left in the buffer \fIanswer\fP of length \fIanslen\fP supplied by the caller. - +.PP The .BR res_nsearch () and @@ -172,7 +172,7 @@ and .B RES_DNSRCH (see description of \fI_res\fP options below). - +.PP The .BR res_nquerydomain () and @@ -180,10 +180,10 @@ and functions make a query using .BR res_nquery ()/ res_query () on the concatenation of \fIname\fP and \fIdomain\fP. - +.PP The following functions are lower-level routines used by .BR res_query ()/ res_query (). - +.PP The .BR res_nmkquery () and @@ -207,7 +207,7 @@ since it has not been supported by DNS servers for a very long time. Notify secondary of SOA (Start of Authority) change. .PP \fInewrr\fP is currently unused. - +.PP The .BR res_nsend () and @@ -479,7 +479,7 @@ T{ .BR dn_expand () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO 4.3BSD. .SH SEE ALSO @@ -488,6 +488,6 @@ T} Thread safety MT-Safe .BR resolver (5), .BR hostname (7), .BR named (8) - +.PP The GNU C library source file .IR resolv/README . diff --git a/man3/rexec.3 b/man3/rexec.3 index 1e7c022a9f..0ebad1276c 100644 --- a/man3/rexec.3 +++ b/man3/rexec.3 @@ -64,7 +64,7 @@ rexec, rexec_af \- return stream to a remote command .SH DESCRIPTION This interface is obsoleted by .BR rcmd (3). - +.PP The .BR rexec () function diff --git a/man3/rint.3 b/man3/rint.3 index 7d472fd478..c20ef94c98 100644 --- a/man3/rint.3 +++ b/man3/rint.3 @@ -107,7 +107,7 @@ checkable via when the result differs in value from the argument. .SH RETURN VALUE These functions return the rounded integer value. - +.PP If .I x is integral, +0, \-0, NaN, or infinite, @@ -152,7 +152,7 @@ of the exponent is smaller than the number of mantissa bits. For the IEEE-754 standard 32-bit and 64-bit floating-point numbers the maximum value of the exponent is 128 (respectively, 1024), and the number of mantissa bits is 24 (respectively, 53).) - +.PP If you want to store the rounded value in an integer type, you probably want to use one of the functions described in .BR lrint (3) diff --git a/man3/round.3 b/man3/round.3 index 732f38271e..50b761cc2b 100644 --- a/man3/round.3 +++ b/man3/round.3 @@ -62,7 +62,7 @@ direction, see .BR fenv (3)), instead of to the nearest even integer like .BR rint (3). - +.PP For example, .IR round(0.5) is 1.0, and @@ -70,7 +70,7 @@ is 1.0, and is \-1.0. .SH RETURN VALUE These functions return the rounded integer value. - +.PP If .I x is integral, +0, \-0, NaN, or infinite, @@ -113,7 +113,7 @@ of the exponent is smaller than the number of mantissa bits. For the IEEE-754 standard 32-bit and 64-bit floating-point numbers the maximum value of the exponent is 128 (respectively, 1024), and the number of mantissa bits is 24 (respectively, 53).) - +.PP If you want to store the rounded value in an integer type, you probably want to use one of the functions described in .BR lround (3) diff --git a/man3/rpc.3 b/man3/rpc.3 index cc46eef0e8..b45283e87d 100644 --- a/man3/rpc.3 +++ b/man3/rpc.3 @@ -1215,7 +1215,7 @@ T} Thread safety MT-Safe .\" We don't have an rpc_secure.3 page in the set at the moment -- MTK, 19 Sep 05 .\" .BR rpc_secure (3), .BR xdr (3) - +.PP The following manuals: .RS Remote Procedure Calls: Protocol Specification @@ -1225,7 +1225,7 @@ Remote Procedure Call Programming Guide rpcgen Programming Guide .br .RE - +.PP .IR "RPC: Remote Procedure Call Protocol Specification" , RFC\ 1050, Sun Microsystems, Inc., USC-ISI. diff --git a/man3/rpmatch.3 b/man3/rpmatch.3 index 2230344310..7f1ab5ca13 100644 --- a/man3/rpmatch.3 +++ b/man3/rpmatch.3 @@ -50,14 +50,14 @@ Feature Test Macro Requirements for glibc (see .BR rpmatch () handles a user response to yes or no questions, with support for internationalization. - +.PP .I response should be a null-terminated string containing a user-supplied response, perhaps obtained with .BR fgets (3) or .BR getline (3). - +.PP The user's language preference is taken into account per the environment variables .BR LANG , @@ -67,7 +67,7 @@ and if the program has called .BR setlocale (3) to effect their changes. - +.PP Regardless of the locale, responses matching .B ^[Yy] are always accepted as affirmative, and those matching @@ -86,7 +86,7 @@ is unrecognized. A return value of \-1 may indicate either an invalid input, or some other error. It is incorrect to only test if the return value is nonzero. - +.PP .BR rpmatch () can fail for any of the reasons that .BR regcomp (3) @@ -111,7 +111,7 @@ T{ .BR rpmatch () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO .BR rpmatch () is not required by any standard, but diff --git a/man3/rtime.3 b/man3/rtime.3 index 579470d6e2..78faf05001 100644 --- a/man3/rtime.3 +++ b/man3/rtime.3 @@ -95,7 +95,7 @@ You may check that the time entry within .I /etc/inetd.conf is not commented out. - +.PP The program connects to a computer called "linux". Using "localhost" does not work. The result is the localtime of the computer "linux". diff --git a/man3/scalb.3 b/man3/scalb.3 index ed55aaa56d..4bd712f71b 100644 --- a/man3/scalb.3 +++ b/man3/scalb.3 @@ -74,7 +74,7 @@ that is: x * FLT_RADIX ** exp .fi - +.PP The definition of .B FLT_RADIX can be obtained by including @@ -87,13 +87,13 @@ On success, these functions return .B FLT_RADIX ** .IR exp . - +.PP If .I x or .I exp is a NaN, a NaN is returned. - +.PP If .I x is positive infinity (negative infinity), @@ -101,13 +101,13 @@ and .I exp is not negative infinity, positive infinity (negative infinity) is returned. - +.PP If .I x is +0 (\-0), and .I exp is not positive infinity, +0 (\-0) is returned. - +.PP If .I x is zero, and @@ -115,7 +115,7 @@ is zero, and is positive infinity, a domain error occurs, and a NaN is returned. - +.PP If .I x is an infinity, @@ -124,7 +124,7 @@ and is negative infinity, a domain error occurs, and a NaN is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -134,7 +134,7 @@ or .BR HUGE_VALL , respectively, with a sign the same as .IR x . - +.PP If the result underflows, a range error occurs, and the functions return zero, with a sign the same as @@ -206,7 +206,7 @@ instead. The .BR scalb () function is from 4.3BSD. - +.PP .BR scalbf () and .BR scalbl () diff --git a/man3/scalbln.3 b/man3/scalbln.3 index 64678aa8ee..c805dc0ccd 100644 --- a/man3/scalbln.3 +++ b/man3/scalbln.3 @@ -81,7 +81,7 @@ that is: x * FLT_RADIX ** exp .fi - +.PP The definition of .B FLT_RADIX can be obtained by including @@ -94,20 +94,20 @@ On success, these functions return .B FLT_RADIX ** .IR exp . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity (negative infinity), positive infinity (negative infinity) is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -117,7 +117,7 @@ or .BR HUGE_VALL , respectively, with a sign the same as .IR x . - +.PP If the result underflows, a range error occurs, and the functions return zero, with a sign the same as @@ -181,7 +181,7 @@ of an integral type, while those in .BR scalb (3) have a second argument of type .IR double . - +.PP If .B FLT_RADIX equals 2 (which is usual), then diff --git a/man3/scandir.3 b/man3/scandir.3 index 2cf370b450..2e469346e9 100644 --- a/man3/scandir.3 +++ b/man3/scandir.3 @@ -144,7 +144,7 @@ The function operates in exactly the same way as .BR scandir (), except for the differences described here. - +.PP If the pathname given in .I dirp is relative, then it is interpreted relative to the directory @@ -154,7 +154,7 @@ referred to by the file descriptor the calling process, as is done by .BR scandir () for a relative pathname). - +.PP If .I dirp is relative and @@ -166,7 +166,7 @@ then is interpreted relative to the current working directory of the calling process (like .BR scandir ()). - +.PP If .I dirp is absolute, then @@ -219,7 +219,7 @@ is a file descriptor referring to a file other than a directory. .SH VERSIONS .BR versionsort () was added to glibc in version 2.1. - +.PP .BR scandirat () was added to glibc in version 2.15. .SH ATTRIBUTES @@ -239,12 +239,12 @@ T{ .BR versionsort () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO .BR alphasort (), .BR scandir (): 4.3BSD, POSIX.1-2008. - +.PP .BR versionsort () and .BR scandirat () @@ -270,7 +270,7 @@ calls .BR strcoll (3); earlier it used .BR strcmp (3). - +.PP Before glibc 2.10, the two arguments of .BR alphasort () and diff --git a/man3/scanf.3 b/man3/scanf.3 index b86f639c64..b26d107da3 100644 --- a/man3/scanf.3 +++ b/man3/scanf.3 @@ -97,7 +97,7 @@ Each .I pointer argument must be of a type that is appropriate for the value returned by the corresponding conversion specification. - +.PP If the number of conversion specifications in .I format exceeds the number of @@ -108,7 +108,7 @@ If the number of arguments exceeds the number of conversion specifications, then the excess .I pointer arguments are evaluated, but are otherwise ignored. - +.PP The .BR scanf () function reads input from the standard input stream @@ -152,7 +152,7 @@ A "failure" can be either of the following: meaning that input characters were unavailable, or .IR "matching failure" , meaning that the input was inappropriate (see below). - +.PP A directive is one of the following: .TP \(bu @@ -537,7 +537,7 @@ On success, these functions return the number of input items successfully matched and assigned; this can be fewer than provided for, or even zero, in the event of an early matching failure. - +.PP The value .B EOF is returned if the end of input is reached before either the first @@ -598,7 +598,7 @@ T{ .BR vfscanf () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO The functions .BR fscanf (), @@ -642,7 +642,7 @@ Thus, one could write the following to have allocate a buffer for an input string, with a pointer to that buffer being returned in .IR *buf : - +.PP char *buf; scanf("%as", &buf); .PP @@ -668,13 +668,13 @@ or is also specified), in which case the .B a is interpreted as a specifier for floating-point numbers (see above). - +.PP Support for the .B m modifier was added to glibc starting with version 2.7, and new programs should use that modifier instead of .BR a . - +.PP As well as being standardized by POSIX, the .B m modifier has the following further advantages over diff --git a/man3/sem_close.3 b/man3/sem_close.3 index 1878b408df..97b8296320 100644 --- a/man3/sem_close.3 +++ b/man3/sem_close.3 @@ -63,7 +63,7 @@ T{ .BR sem_close () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES diff --git a/man3/sem_destroy.3 b/man3/sem_destroy.3 index 17eb686a90..6980e1a7c5 100644 --- a/man3/sem_destroy.3 +++ b/man3/sem_destroy.3 @@ -38,17 +38,17 @@ Link with \fI\-pthread\fP. .BR sem_destroy () destroys the unnamed semaphore at the address pointed to by .IR sem . - +.PP Only a semaphore that has been initialized by .BR sem_init (3) should be destroyed using .BR sem_destroy (). - +.PP Destroying a semaphore that other processes or threads are currently blocked on (in .BR sem_wait (3)) produces undefined behavior. - +.PP Using a semaphore that has been destroyed produces undefined results, until the semaphore has been reinitialized using .BR sem_init (3). diff --git a/man3/sem_getvalue.3 b/man3/sem_getvalue.3 index 31366bdfc1..1219a42903 100644 --- a/man3/sem_getvalue.3 +++ b/man3/sem_getvalue.3 @@ -40,7 +40,7 @@ places the current value of the semaphore pointed to .I sem into the integer pointed to by .IR sval . - +.PP If one or more processes or threads are blocked waiting to lock the semaphore with .BR sem_wait (3), diff --git a/man3/sem_init.3 b/man3/sem_init.3 index 2229ee8455..4da615ebfb 100644 --- a/man3/sem_init.3 +++ b/man3/sem_init.3 @@ -41,12 +41,12 @@ initializes the unnamed semaphore at the address pointed to by The .I value argument specifies the initial value for the semaphore. - +.PP The .I pshared argument indicates whether this semaphore is to be shared between the threads of a process, or between processes. - +.PP If .I pshared has the value 0, @@ -54,7 +54,7 @@ then the semaphore is shared between the threads of a process, and should be located at some address that is visible to all threads (e.g., a global variable, or a variable allocated dynamically on the heap). - +.PP If .I pshared is nonzero, then the semaphore is shared between processes, @@ -71,7 +71,7 @@ can operate on the semaphore using .BR sem_post (3), .BR sem_wait (3), and so on. - +.PP Initializing a semaphore that has already been initialized results in undefined behavior. .SH RETURN VALUE diff --git a/man3/sem_open.3 b/man3/sem_open.3 index de297e5aac..b531b21c87 100644 --- a/man3/sem_open.3 +++ b/man3/sem_open.3 @@ -47,7 +47,7 @@ For details of the construction of .IR name , see .BR sem_overview (7). - +.PP The .I oflag argument specifies flags that control the operation of the call. @@ -179,7 +179,7 @@ T{ .BR sem_open () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/sem_wait.3 b/man3/sem_wait.3 index f22ff020c8..9a0320c5ef 100644 --- a/man3/sem_wait.3 +++ b/man3/sem_wait.3 @@ -56,7 +56,7 @@ If the semaphore currently has the value zero, then the call blocks until either it becomes possible to perform the decrement (i.e., the semaphore value rises above zero), or a signal handler interrupts the call. - +.PP .BR sem_trywait () is the same as .BR sem_wait (), @@ -66,7 +66,7 @@ then call returns an error set to .BR EAGAIN ) instead of blocking. - +.PP .BR sem_timedwait () is the same as .BR sem_wait (), @@ -79,7 +79,7 @@ The argument points to a structure that specifies an absolute timeout in seconds and nanoseconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC). This structure is defined as follows: - +.PP .nf .in +4n struct timespec { @@ -97,7 +97,7 @@ fails with a timeout error .RI ( errno set to .BR ETIMEDOUT ). - +.PP If the operation can be performed immediately, then .BR sem_timedwait () never fails with a timeout error, regardless of the value of @@ -175,7 +175,7 @@ The second command-line argument specifies the length of the timeout, in seconds, for .BR sem_timedwait (). The following shows what happens on two different runs of the program: - +.PP .in +4n .nf .RB "$" " ./a.out 2 3" diff --git a/man3/setbuf.3 b/man3/setbuf.3 index 61df9f256d..918445e4fa 100644 --- a/man3/setbuf.3 +++ b/man3/setbuf.3 @@ -86,7 +86,7 @@ The function may be used to force the block out early. (See .BR fclose (3).) - +.PP Normally all files are block buffered. If a stream refers to a terminal (as .I stdout @@ -160,7 +160,7 @@ is invalid or the request cannot be honored). It may set .I errno on failure. - +.PP The other functions do not return a value. .SH ATTRIBUTES For an explanation of the terms used in this section, see diff --git a/man3/setenv.3 b/man3/setenv.3 index 8291a928a0..3f5c8b8bba 100644 --- a/man3/setenv.3 +++ b/man3/setenv.3 @@ -110,7 +110,7 @@ function returns zero on success, or \-1 on error, with .I errno set to indicate the cause of the error. - +.PP The .BR unsetenv () function returns zero on success, @@ -149,7 +149,7 @@ POSIX.1 does not require or .BR unsetenv () to be reentrant. - +.PP Prior to glibc 2.2.2, .BR unsetenv () was prototyped diff --git a/man3/setlocale.3 b/man3/setlocale.3 index 265ac2f67e..17c343f1bd 100644 --- a/man3/setlocale.3 +++ b/man3/setlocale.3 @@ -183,7 +183,7 @@ T{ .BR setlocale () T} Thread safety MT-Unsafe const:locale env .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99. .SH SEE ALSO diff --git a/man3/setlogmask.3 b/man3/setlogmask.3 index f2038d3c64..1be0849120 100644 --- a/man3/setlogmask.3 +++ b/man3/setlogmask.3 @@ -84,7 +84,7 @@ T{ .BR setlogmask () T} Thread safety MT-Unsafe race:LogMask .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .\" Note that the description in POSIX.1-2001 is flawed. diff --git a/man3/setnetgrent.3 b/man3/setnetgrent.3 index 353e903126..6c70a8a9ab 100644 --- a/man3/setnetgrent.3 +++ b/man3/setnetgrent.3 @@ -122,7 +122,7 @@ MT-Unsafe race:netgrent race:netgrentbuf locale T} .TE - +.sp 1 In the above table, .I netgrent in diff --git a/man3/shm_open.3 b/man3/shm_open.3 index 251c58fb7d..df89a1a72a 100644 --- a/man3/shm_open.3 +++ b/man3/shm_open.3 @@ -141,7 +141,7 @@ The flag (see .BR fcntl (2)) is set for the file descriptor. - +.PP The file descriptor is normally used in subsequent calls to .BR ftruncate (2) @@ -150,7 +150,7 @@ to After a call to .BR mmap (2) the file descriptor may be closed without affecting the memory mapping. - +.PP The operation of .BR shm_unlink () @@ -260,7 +260,7 @@ T{ .BR shm_unlink () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .LP diff --git a/man3/signbit.3 b/man3/signbit.3 index 4a5b18f283..599e6cd893 100644 --- a/man3/signbit.3 +++ b/man3/signbit.3 @@ -44,7 +44,7 @@ The comparison is false, but .IR "signbit(\-0.0)" will return a nonzero value. - +.PP NaNs and infinities have a sign bit. .SH RETURN VALUE The diff --git a/man3/significand.3 b/man3/significand.3 index 3c33635970..4421fc1754 100644 --- a/man3/significand.3 +++ b/man3/significand.3 @@ -63,7 +63,7 @@ T{ .BR significandl () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO These functions are nonstandard; the .I double diff --git a/man3/sigpause.3 b/man3/sigpause.3 index 4dc661f5a8..df5eeb2156 100644 --- a/man3/sigpause.3 +++ b/man3/sigpause.3 @@ -98,7 +98,7 @@ argument (instead of an .SS Linux notes On Linux, this routine is a system call only on the Sparc (sparc64) architecture. - +.PP .\" Libc4 and libc5 know only about the BSD version. .\" Glibc uses the BSD version if the diff --git a/man3/sigqueue.3 b/man3/sigqueue.3 index cc30804fb4..4d77a37230 100644 --- a/man3/sigqueue.3 +++ b/man3/sigqueue.3 @@ -66,7 +66,7 @@ union sigval { }; .fi .in - +.PP If the receiving process has installed a handler for this signal using the .B SA_SIGINFO flag to diff --git a/man3/sigset.3 b/man3/sigset.3 index 874c8d1850..afb80d89cf 100644 --- a/man3/sigset.3 +++ b/man3/sigset.3 @@ -62,7 +62,7 @@ This API is obsolete: new applications should use the POSIX signal API .RB ( sigaction (2), .BR sigprocmask (2), etc.) - +.PP The .BR sigset () function modifies the disposition of the signal @@ -113,13 +113,13 @@ The function adds .I sig to the calling process's signal mask. - +.PP The .BR sigrelse () function removes .I sig from the calling process's signal mask. - +.PP The .BR sigignore () function sets the disposition of @@ -142,7 +142,7 @@ returns \-1, with .I errno set to indicate the error. (But see BUGS below.) - +.PP The .BR sighold (), .BR sigrelse (), @@ -158,14 +158,14 @@ see the ERRORS under .BR sigaction (2) and .BR sigprocmask (2). - +.PP For .BR sighold () and .BR sigrelse () see the ERRORS under .BR sigprocmask (2). - +.PP For .BR sigignore (), see the errors under @@ -205,13 +205,13 @@ and instead. .SH NOTES These functions appeared in glibc version 2.1. - +.PP The .I sighandler_t type is a GNU extension; it is used on this page only to make the .BR sigset () prototype more easily readable. - +.PP The .BR sigset () function provides reliable signal handling semantics (as when calling @@ -219,7 +219,7 @@ function provides reliable signal handling semantics (as when calling with .I sa_mask equal to 0). - +.PP On System V, the .BR signal () function provides unreliable semantics (as when calling @@ -237,7 +237,7 @@ unspecified. See .BR signal (2) for further details. - +.PP In order to wait for a signal, BSD and System V both provided a function named .BR sigpause (3), @@ -254,7 +254,7 @@ if .I disp was specified as a value other than .BR SIG_HOLD . - +.PP In versions of glibc before 2.5, .BR sigset () does not correctly return the previous disposition of the signal diff --git a/man3/sigvec.3 b/man3/sigvec.3 index f8bc2f983c..be0a989827 100644 --- a/man3/sigvec.3 +++ b/man3/sigvec.3 @@ -56,7 +56,7 @@ This API is obsolete: new applications should use the POSIX signal API .RB ( sigaction (2), .BR sigprocmask (2), etc.). - +.PP The .BR sigvec () function sets and/or gets the disposition of the signal @@ -81,13 +81,13 @@ without changing it, specify NULL for .IR vec , and a non-null pointer for .IR ovec . - +.PP The dispositions for .B SIGKILL and .B SIGSTOP cannot be changed. - +.PP The .I sigvec structure has the following form: @@ -110,7 +110,7 @@ the address of a signal handler function; meaning the default disposition applies for the signal; or .BR SIG_IGN , meaning that the signal is ignored. - +.PP If .I sv_handler specifies the address of a signal handler, then @@ -124,7 +124,7 @@ Attempts to block or .B SIGSTOP are silently ignored. - +.PP If .I sv_handler specifies the address of a signal handler, then the @@ -205,13 +205,13 @@ The function returns 0 on success; on error, it returns \-1 and sets .I errno to indicate the error. - +.PP The .BR sigblock () and .BR sigsetmask () functions return the previous signal mask. - +.PP The .BR sigmask () macro returns the signal mask for @@ -267,7 +267,7 @@ unspecified. See .BR signal (2) for further details. - +.PP In order to wait for a signal, BSD and System V both provided a function named .BR sigpause (3), diff --git a/man3/sin.3 b/man3/sin.3 index 3fb50f6230..2c6f171abd 100644 --- a/man3/sin.3 +++ b/man3/sin.3 @@ -72,11 +72,11 @@ given in radians. .SH RETURN VALUE On success, these functions return the sine of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity or negative infinity, @@ -117,7 +117,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/sincos.3 b/man3/sincos.3 index f4087c1d69..fb0b295bf7 100644 --- a/man3/sincos.3 +++ b/man3/sincos.3 @@ -29,7 +29,7 @@ These functions compute both at the same time, and store the results in .I *sin and .IR *cos . - +.PP If .I x is a NaN, @@ -37,7 +37,7 @@ a NaN is returned in .I *sin and .IR *cos . - +.PP If .I x is positive infinity or negative infinity, diff --git a/man3/sinh.3 b/man3/sinh.3 index 39c0bc4da1..e571b3c017 100644 --- a/man3/sinh.3 +++ b/man3/sinh.3 @@ -75,20 +75,20 @@ is defined mathematically as: .SH RETURN VALUE On success, these functions return the hyperbolic sine of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is positive infinity (negative infinity), positive infinity (negative infinity) is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -133,7 +133,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/sleep.3 b/man3/sleep.3 index 51b4c2a3cd..83014eb7be 100644 --- a/man3/sleep.3 +++ b/man3/sleep.3 @@ -54,7 +54,7 @@ T{ .BR sleep () T} Thread safety MT-Unsafe sig:SIGCHLD/linux .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH NOTES diff --git a/man3/sockatmark.3 b/man3/sockatmark.3 index d1612ec0d3..4eabefc096 100644 --- a/man3/sockatmark.3 +++ b/man3/sockatmark.3 @@ -91,14 +91,14 @@ returns 1, then the out-of-band data can be read using the .B MSG_OOB flag of .BR recv (2). - +.PP Out-of-band data is supported only on some stream socket protocols. - +.PP .BR sockatmark () can safely be called from a handler for the .B SIGURG signal. - +.PP .BR sockatmark () is implemented using the .B SIOCATMARK diff --git a/man3/sqrt.3 b/man3/sqrt.3 index 53b5b47baf..daec0ec928 100644 --- a/man3/sqrt.3 +++ b/man3/sqrt.3 @@ -67,19 +67,19 @@ These functions return the nonnegative square root of .SH RETURN VALUE On success, these functions return the square root of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is positive infinity, positive infinity is returned. - +.PP If .I x is less than \-0, @@ -116,7 +116,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/statvfs.3 b/man3/statvfs.3 index f9ca32ec70..8f36837f3a 100644 --- a/man3/statvfs.3 +++ b/man3/statvfs.3 @@ -46,7 +46,7 @@ is the pathname of any file within the mounted filesystem. is a pointer to a .I statvfs structure defined approximately as follows: - +.PP .in +4n .nf struct statvfs { @@ -66,7 +66,7 @@ struct statvfs { }; .fi .in - +.PP Here the types .I fsblkcnt_t and @@ -75,7 +75,7 @@ are defined in .IR <sys/types.h> . Both used to be .IR "unsigned long" . - +.PP The field .I f_flag is a bit mask indicating various options that were employed @@ -121,7 +121,7 @@ in .LP It is unspecified whether all members of the returned struct have meaningful values on all filesystems. - +.PP .BR fstatvfs () returns the same information about an open file referenced by descriptor .IR fd . @@ -202,7 +202,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. - +.PP Only the .B ST_NOSUID and @@ -218,7 +218,7 @@ The Linux kernel has system calls and .BR fstatfs (2) to support this library call. - +.PP In glibc versions before 2.13, .\" glibc commit 3cdaa6adb113a088fdfb87aa6d7747557eccc58d .BR statvfs () @@ -234,7 +234,7 @@ field, and since glibc version 2.13, the .BR statvfs () function will use information from that field rather than scanning .IR /proc/mounts . - +.PP The glibc implementations of .sp .nf diff --git a/man3/stdarg.3 b/man3/stdarg.3 index 3691a7eccd..dee35cb280 100644 --- a/man3/stdarg.3 +++ b/man3/stdarg.3 @@ -169,7 +169,7 @@ argument, followed by the same number of .BR va_arg () invocations that was used to reach the current state of .IR src . - +.PP .\" Proposal from clive@demon.net, 1997-02-28 An obvious implementation would have a .I va_list diff --git a/man3/stdin.3 b/man3/stdin.3 index ee72e45910..fc9990ff8d 100644 --- a/man3/stdin.3 +++ b/man3/stdin.3 @@ -42,7 +42,7 @@ used to refer to these files, namely .IR stdout , and .IR stderr . - +.PP Each of these symbols is a .BR stdio (3) macro of type pointer to diff --git a/man3/strcasecmp.3 b/man3/strcasecmp.3 index f326a7df9f..1818cfc38e 100644 --- a/man3/strcasecmp.3 +++ b/man3/strcasecmp.3 @@ -103,9 +103,9 @@ header file also declares these functions, if the (or, in glibc 2.19 and earlier, .BR _BSD_SOURCE ) feature test macro is defined. - +.PP The POSIX.1-2008 standard says of these functions: - +.PP .RS When the .B LC_CTYPE diff --git a/man3/strcat.3 b/man3/strcat.3 index 8e84af82f0..319248ca8c 100644 --- a/man3/strcat.3 +++ b/man3/strcat.3 @@ -99,7 +99,7 @@ Therefore, the size of .I dest must be at least .IR "strlen(dest)+n+1" . - +.PP A simple implementation of .BR strncat () might be: @@ -144,9 +144,9 @@ T} Thread safety MT-Safe POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. .SH NOTES Some systems (the BSDs, Solaris, and others) provide the following function: - +.PP size_t strlcat(char *dest, const char *src, size_t size); - +.PP This function appends the null-terminated string .I src to the string diff --git a/man3/strchr.3 b/man3/strchr.3 index 606578ed79..0cde6d34bf 100644 --- a/man3/strchr.3 +++ b/man3/strchr.3 @@ -90,7 +90,7 @@ so that if .I c is specified as \(aq\\0\(aq, these functions return a pointer to the terminator. - +.PP The .BR strchrnul () function returns a pointer to @@ -122,7 +122,7 @@ T} Thread safety MT-Safe .BR strchr (), .BR strrchr (): POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. - +.PP .BR strchrnul () is a GNU extension. .SH SEE ALSO diff --git a/man3/strcoll.3 b/man3/strcoll.3 index d565278938..b9501507b4 100644 --- a/man3/strcoll.3 +++ b/man3/strcoll.3 @@ -78,7 +78,7 @@ T{ .BR strcoll () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. .SH NOTES diff --git a/man3/strcpy.3 b/man3/strcpy.3 index 661b1363d4..a620575cdb 100644 --- a/man3/strcpy.3 +++ b/man3/strcpy.3 @@ -141,7 +141,7 @@ the length of then .BR strcpy () can be used. - +.PP One valid (and intended) use of .BR strncpy () is to copy a C string to a fixed-length buffer @@ -150,7 +150,7 @@ and that unused bytes in the target buffer are zeroed out (perhaps to prevent information leaks if the buffer is to be written to media or transmitted to another process via an interprocess communication technique). - +.PP If there is no terminating null byte in the first .I n bytes of @@ -181,9 +181,9 @@ bytes, information is lost in the copying to .\" .SS strlcpy() Some systems (the BSDs, Solaris, and others) provide the following function: - +.PP size_t strlcpy(char *dest, const char *src, size_t size); - +.PP .\" http://static.usenix.org/event/usenix99/full_papers/millert/millert_html/index.html .\" "strlcpy and strlcat - consistent, safe, string copy and concatenation" .\" 1999 USENIX Annual Technical Conference diff --git a/man3/strdup.3 b/man3/strdup.3 index e6e59d58b4..a599555ff0 100644 --- a/man3/strdup.3 +++ b/man3/strdup.3 @@ -85,7 +85,7 @@ obtained with .BR malloc (3), and can be freed with .BR free (3). - +.PP The .BR strndup () function is similar, but copies at most @@ -98,7 +98,7 @@ is longer than only .I n bytes are copied, and a terminating null byte (\(aq\\0\(aq) is added. - +.PP .BR strdupa () and .BR strndupa () @@ -136,7 +136,7 @@ T{ .BR strndupa () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO .\" 4.3BSD-Reno, not (first) 4.3BSD. .BR strdup () diff --git a/man3/strerror.3 b/man3/strerror.3 index 6692b824e5..659eb687f9 100644 --- a/man3/strerror.3 +++ b/man3/strerror.3 @@ -113,7 +113,7 @@ is defined by default with the value 200112L, so that the XSI-compliant version of .BR strerror_r () is provided by default. - +.PP The XSI-compliant .BR strerror_r () is preferred for portable applications. @@ -121,7 +121,7 @@ It returns the error string in the user-supplied buffer .I buf of length .IR buflen . - +.PP The GNU-specific .BR strerror_r () returns a pointer to a string containing the error message. @@ -166,7 +166,7 @@ and the GNU-specific functions return the appropriate error description string, or an "Unknown error nnn" message if the error number is unknown. - +.PP The XSI-compliant .BR strerror_r () function returns 0 on success. @@ -175,7 +175,7 @@ a (positive) error number is returned (since glibc 2.13), or \-1 is returned and .I errno is set to indicate the error (glibc versions before 2.13). - +.PP POSIX.1-2001 and POSIX.1-2008 require that a successful call to .BR strerror () or @@ -229,14 +229,14 @@ is specified by POSIX.1-2001 and POSIX.1-2008. .\" A future POSIX.1 may remove strerror_r() .\" http://austingroupbugs.net/tag_view_page.php?tag_id=8 .\" http://austingroupbugs.net/view.php?id=508 - +.PP .BR strerror_l () is specified in POSIX.1-2008. - +.PP The GNU-specific .BR strerror_r () function is a nonstandard extension. - +.PP POSIX.1-2001 permits .BR strerror () to set diff --git a/man3/strfmon.3 b/man3/strfmon.3 index ea79b4f3c7..c4eb219199 100644 --- a/man3/strfmon.3 +++ b/man3/strfmon.3 @@ -46,7 +46,7 @@ result in the character array .I s of size .IR max . - +.PP The .BR strfmon_l () function performs the same task, @@ -172,7 +172,7 @@ T{ .BR strfmon_l () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. .SH EXAMPLE @@ -187,9 +187,9 @@ strfmon(buf, sizeof(buf), "[%^=*#6n] [%=*#6i]", .in outputs .in +4n - +.PP [€ **1234,57] [EUR **1 234,57] - +.PP .in in the .I nl_NL @@ -202,7 +202,7 @@ and .I en_GB locales yield .in +4n - +.PP [ **1234,57 €] [ **1.234,57 EUR] .br [ Fr. **1234.57] [ CHF **1'234.57] diff --git a/man3/strfromd.3 b/man3/strfromd.3 index 1888a6510b..1563792507 100644 --- a/man3/strfromd.3 +++ b/man3/strfromd.3 @@ -83,9 +83,9 @@ The and .BR strfroml () functions are equivalent to - +.PP snprintf(str, n, format, fp); - +.PP except for the .I format string. @@ -119,7 +119,7 @@ for a detailed description of these conversion specifiers. .sp The implementation conforms to the C99 standard on conversion of NaN and infinity values: - +.PP .RS If .I fp @@ -143,7 +143,7 @@ Likewise if .I fp is infinity, it is converted to [-]inf or [-]INF. .RE - +.PP A malformed .I format string results in undefined behavior. diff --git a/man3/strftime.3 b/man3/strftime.3 index fe56733c92..04f313e1b3 100644 --- a/man3/strftime.3 +++ b/man3/strftime.3 @@ -460,7 +460,7 @@ as well. The .B %F conversion is in C99 and POSIX.1-2001. - +.PP In SUSv2, the .B %S specifier allowed a range of 00 to 61, @@ -509,7 +509,7 @@ may be specified. or .B O modifiers, if present.) - +.PP The following flag characters are permitted: .TP .B _ @@ -554,7 +554,7 @@ specify any .I errno settings for .BR strftime (). - +.PP Some buggy versions of .BR gcc (1) complain about the use of @@ -580,7 +580,7 @@ my_strftime(char *s, size_t max, const char *fmt, } .fi .in - +.PP Nowadays, .BR gcc (1) provides the diff --git a/man3/strptime.3 b/man3/strptime.3 index 48c999abfa..f6b362aa0a 100644 --- a/man3/strptime.3 +++ b/man3/strptime.3 @@ -51,7 +51,7 @@ structure pointed to by .IR tm , using the format specified by .IR format . - +.PP The broken-down time structure .I tm is defined in @@ -73,12 +73,12 @@ struct tm { }; .fi .in - +.PP For more details on the .I tm structure, see .BR ctime (3). - +.PP The .I format argument diff --git a/man3/strsignal.3 b/man3/strsignal.3 index afeb1dc133..56c510d01e 100644 --- a/man3/strsignal.3 +++ b/man3/strsignal.3 @@ -93,7 +93,7 @@ T{ .BR strsignal () T} Thread safety MT-Unsafe race:strsignal locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008. Present on Solaris and the BSDs. diff --git a/man3/strstr.3 b/man3/strstr.3 index e6a9f2b2cb..3149d8f04a 100644 --- a/man3/strstr.3 +++ b/man3/strstr.3 @@ -53,7 +53,7 @@ function finds the first occurrence of the substring in the string .IR haystack . The terminating null bytes (\(aq\\0\(aq) are not compared. - +.PP The .BR strcasestr () function is like @@ -80,7 +80,7 @@ T} Thread safety MT-Safe locale .SH CONFORMING TO .BR strstr (): POSIX.1-2001, POSIX.1-2008, C89, C99. - +.PP The .BR strcasestr () function is a nonstandard extension. diff --git a/man3/strtod.3 b/man3/strtod.3 index 0b6aaf3d28..6bce66ef33 100644 --- a/man3/strtod.3 +++ b/man3/strtod.3 @@ -80,7 +80,7 @@ to and .I long double representation, respectively. - +.PP The expected form of the (initial portion of the) string is optional leading white space as recognized by .BR isspace (3), @@ -122,21 +122,21 @@ specifies in an implementation-dependent way the type of NAN (see NOTES). .SH RETURN VALUE These functions return the converted value, if any. - +.PP If .I endptr is not NULL, a pointer to the character after the last character used in the conversion is stored in the location referenced by .IR endptr . - +.PP If no conversion is performed, zero is returned and (unless .I endptr is null) the value of .I nptr is stored in the location referenced by .IR endptr . - +.PP If the correct value would cause overflow, plus or minus .B HUGE_VAL .RB ( HUGE_VALF , @@ -170,7 +170,7 @@ T} Thread safety MT-Safe locale .TE .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. - +.PP .BR strtod () was also described in C89. .SH NOTES @@ -182,7 +182,7 @@ to 0 before the call, and then determine if an error occurred by checking whether .I errno has a nonzero value after the call. - +.PP In the glibc implementation, the .IR n-char-sequence that optionally follows "NAN" diff --git a/man3/strtok.3 b/man3/strtok.3 index 328df33abd..35472d835a 100644 --- a/man3/strtok.3 +++ b/man3/strtok.3 @@ -63,7 +63,7 @@ specified in In each subsequent call that should parse the same string, .I str must be NULL. - +.PP The .I delim argument specifies a set of bytes that @@ -72,7 +72,7 @@ The caller may specify different strings in .I delim in successive calls that parse the same string. - +.PP Each call to .BR strtok () returns a pointer to a @@ -81,7 +81,7 @@ This string does not include the delimiting byte. If no more tokens are found, .BR strtok () returns NULL. - +.PP A sequence of calls to .BR strtok () that operate on the same string maintains a pointer @@ -101,7 +101,7 @@ returns NULL. will thus cause .BR strtok () to return NULL on the first call.) - +.PP The end of each token is found by scanning forward until either the next delimiter byte is found or until the terminating null byte (\(aq\\0\(aq) is encountered. @@ -114,7 +114,7 @@ when searching for the next token. In this case, .BR strtok () returns a pointer to the start of the found token. - +.PP From the above description, it follows that a sequence of two or more contiguous delimiter bytes in the parsed string is considered to be a single delimiter, and that @@ -128,7 +128,7 @@ successive calls to that specify the delimiter string "\fI;,\fP" would return the strings "\fIaaa\fP" and "\fIbbb\fP", and then a null pointer. - +.PP The .BR strtok_r () function is a reentrant version @@ -141,7 +141,7 @@ variable that is used internally by .BR strtok_r () in order to maintain context between successive calls that parse the same string. - +.PP On the first call to .BR strtok_r (), .I str @@ -153,7 +153,7 @@ In subsequent calls, should be NULL, and .I saveptr should be unchanged since the previous call. - +.PP Different strings may be parsed concurrently using sequences of calls to .BR strtok_r () that specify different diff --git a/man3/strtol.3 b/man3/strtol.3 index 3b2de73cc5..fe53118a09 100644 --- a/man3/strtol.3 +++ b/man3/strtol.3 @@ -172,7 +172,7 @@ T} Thread safety MT-Safe locale .SH CONFORMING TO .BR strtol (): POSIX.1-2001, POSIX.1-2008, C89, C99 SVr4, 4.3BSD. - +.PP .BR strtoll (): POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES @@ -193,7 +193,7 @@ to 0 before the call, and then determine if an error occurred by checking whether .I errno has a nonzero value after the call. - +.PP According to POSIX.1, in locales other than the "C" and "POSIX", these functions may accept other, diff --git a/man3/strtoul.3 b/man3/strtoul.3 index cc60feb01f..25b44a269e 100644 --- a/man3/strtoul.3 +++ b/man3/strtoul.3 @@ -176,7 +176,7 @@ T} Thread safety MT-Safe locale .SH CONFORMING TO .BR strtoul (): POSIX.1-2001, POSIX.1-2008, C89, C99 SVr4. - +.PP .BR strtoull (): POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES @@ -193,7 +193,7 @@ to 0 before the call, and then determine if an error occurred by checking whether .I errno has a nonzero value after the call. - +.PP In locales other than the "C" locale, other strings may be accepted. (For example, the thousands separator of the current locale may be supported.) @@ -212,7 +212,7 @@ may be equivalent to .BR strtoull () or to .BR strtoul (). - +.PP Negative values are considered valid input and are silently converted to the equivalent .I "unsigned long int" diff --git a/man3/syslog.3 b/man3/syslog.3 index 21bbd56638..e4cf4d8226 100644 --- a/man3/syslog.3 +++ b/man3/syslog.3 @@ -62,7 +62,7 @@ Feature Test Macro Requirements for glibc (see .SS openlog() .BR openlog () opens a connection to the system logger for a program. - +.PP The string pointed to by .I ident is prepended to every message, and is typically set to the program name. @@ -72,7 +72,7 @@ is NULL, the program name is used. (POSIX.1-2008 does not specify the behavior when .I ident is NULL.) - +.PP The .I option argument specifies flags which control the operation of @@ -89,7 +89,7 @@ The values that may be specified for and .I facility are described below. - +.PP The use of .BR openlog () is optional; it will automatically be called by @@ -102,7 +102,7 @@ will default to NULL. .BR syslog () generates a log message, which will be distributed by .BR syslogd (8). - +.PP The .I priority argument is formed by ORing together a @@ -121,7 +121,7 @@ is used, or, if there was no preceding call, a default of .BR LOG_USER is employed. - +.PP The remaining arguments are a .IR format , as in @@ -134,7 +134,7 @@ will be replaced by the error message string .IR strerror ( errno ). The format string need not include a terminating newline character. - +.PP The function .BR vsyslog () performs the same task as @@ -298,7 +298,7 @@ and (but not .BR vsyslog ()) are specified in SUSv2, POSIX.1-2001, and POSIX.1-2008. - +.PP POSIX.1-2001 specifies only the .B LOG_USER and @@ -312,7 +312,7 @@ and the other .I facility values appear on most UNIX systems. - +.PP The .B LOG_PERROR value for diff --git a/man3/system.3 b/man3/system.3 index 3ee45ebf25..36d0f99be7 100644 --- a/man3/system.3 +++ b/man3/system.3 @@ -47,12 +47,12 @@ to create a child process that executes the shell command specified in using .BR execl (3) as follows: - +.PP execl("/bin/sh", "sh", "-c", command, (char *) 0); - +.PP .BR system () returns after the command has been completed. - +.PP During execution of the command, .B SIGCHLD will be blocked, and @@ -64,7 +64,7 @@ will be ignored, in the process that calls (these signals will be handled according to their defaults inside the child process that executes .IR command ). - +.PP If .I command is NULL, then @@ -138,7 +138,7 @@ The main cost of is inefficiency: additional system calls are required to create the process that runs the shell and to execute the shell. - +.PP If the .B _XOPEN_SOURCE feature test macro is defined @@ -191,13 +191,13 @@ set-group-ID privileges on systems on which is bash version 2, since bash 2 drops privileges on startup. (Debian uses a modified bash which does not do this when invoked as .BR sh .) - +.PP According to POSIX.1, it is unspecified whether handlers registered using .BR pthread_atfork (3) are called during the execution of .BR system (). In the glibc implementation, such handlers are not called. - +.PP In versions of glibc before 2.1.3, the check for the availability of .I /bin/sh was not actually performed if diff --git a/man3/sysv_signal.3 b/man3/sysv_signal.3 index b29fd8f944..a7f0330640 100644 --- a/man3/sysv_signal.3 +++ b/man3/sysv_signal.3 @@ -38,7 +38,7 @@ The .BR sysv_signal () function takes the same arguments, and performs the same task, as .BR signal (2). - +.PP However .BR sysv_signal () provides the System V unreliable signal semantics, that is: @@ -77,7 +77,7 @@ Use of should be avoided; use .BR sigaction (2) instead. - +.PP On older Linux systems, .BR sysv_signal () and @@ -88,7 +88,7 @@ But on newer systems, provides reliable signal semantics; see .BR signal (2) for details. - +.PP The use of .I sighandler_t is a GNU extension; diff --git a/man3/tan.3 b/man3/tan.3 index 95a892c1f3..3803b6bcd8 100644 --- a/man3/tan.3 +++ b/man3/tan.3 @@ -72,17 +72,17 @@ given in radians. .SH RETURN VALUE On success, these functions return the tangent of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity or negative infinity, a domain error occurs, and a NaN is returned. - +.PP If the correct result would overflow, a range error occurs, and the functions return @@ -142,7 +142,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/tanh.3 b/man3/tanh.3 index 9aef7cb70d..49ccabf132 100644 --- a/man3/tanh.3 +++ b/man3/tanh.3 @@ -74,15 +74,15 @@ is defined mathematically as: .SH RETURN VALUE On success, these functions return the hyperbolic tangent of .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is +0 (\-0), +0 (\-0) is returned. - +.PP If .I x is positive infinity (negative infinity), @@ -109,7 +109,7 @@ T} Thread safety MT-Safe .TE .SH CONFORMING TO C99, POSIX.1-2001, POSIX.1-2008. - +.PP The variant returning .I double also conforms to diff --git a/man3/telldir.3 b/man3/telldir.3 index 64d02a3475..38339e3c77 100644 --- a/man3/telldir.3 +++ b/man3/telldir.3 @@ -85,7 +85,7 @@ was POSIX.1-2001 specifies .IR long , and this is the type used since glibc 2.1.2. - +.PP In early filesystems, the value returned by .BR telldir () was a simple file offset within a directory. diff --git a/man3/tempnam.3 b/man3/tempnam.3 index a424932b92..cc91268410 100644 --- a/man3/tempnam.3 +++ b/man3/tempnam.3 @@ -49,7 +49,7 @@ Use or .BR tmpfile (3) instead. - +.PP The .BR tempnam () function returns a pointer to a string that is a valid filename, @@ -63,7 +63,7 @@ in case is a non-NULL string of at most five bytes. The directory prefix part of the pathname generated is required to be "appropriate" (often that at least implies writable). - +.PP Attempts to find an appropriate directory go through the following steps: .TP 3 @@ -141,7 +141,7 @@ Or better yet, use .BR mkstemp (3) or .BR tmpfile (3). - +.PP SUSv2 does not mention the use of .BR TMPDIR ; glibc will use it only @@ -171,7 +171,7 @@ the behavior is implementation defined. .BR tempnam () uses at most the first five bytes from .IR pfx . - +.PP The glibc implementation of .BR tempnam () will fail with the error diff --git a/man3/termios.3 b/man3/termios.3 index 4520572193..fe00a0951a 100644 --- a/man3/termios.3 +++ b/man3/termios.3 @@ -149,7 +149,7 @@ the program might confuse it with the prefix that marks a parity error. Therefore, a valid byte \\377 is passed to the program as two bytes, \\377 \\377, in this case. - +.IP If neither \fBIGNPAR\fP nor \fBPARMRK\fP is set, read a character with a parity error or framing error as \\0. @@ -708,7 +708,7 @@ unset). By default, .B ICANON is set. - +.PP In canonical mode: .IP * 2 Input is made available line by line. @@ -910,7 +910,7 @@ The new values do not take effect until .BR tcsetattr () is successfully called. - +.PP Setting the speed to \fBB0\fP instructs the modem to "hang up". The actual bit rate corresponding to \fBB38400\fP may be altered with .BR setserial (8). @@ -1050,7 +1050,7 @@ T} Thread safety MT-Safe and .BR cfsetospeed () are specified in POSIX.1-2001. - +.PP .BR cfmakeraw () and .BR cfsetspeed () diff --git a/man3/tgamma.3 b/man3/tgamma.3 index d0ac21dc47..657ec2cb0d 100644 --- a/man3/tgamma.3 +++ b/man3/tgamma.3 @@ -41,7 +41,7 @@ _POSIX_C_SOURCE\ >=\ 200112L .SH DESCRIPTION These functions calculate the Gamma function of .IR x . - +.PP The Gamma function is defined by .sp Gamma(x) = integral from 0 to infinity of t^(x\-1) e^\-t dt @@ -66,21 +66,21 @@ outside the poles: .PP .SH RETURN VALUE On success, these functions return Gamma(x). - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is positive infinity, positive infinity is returned. - +.PP If .I x is a negative integer, or is negative infinity, a domain error occurs, and a NaN is returned. - +.PP If the result overflows, a range error occurs, and the functions return @@ -89,11 +89,11 @@ and the functions return or .BR HUGE_VALL , respectively, with the correct mathematical sign. - +.PP If the result underflows, a range error occurs, and the functions return 0, with the correct mathematical sign. - +.PP If .I x is \-0 or +0, @@ -186,7 +186,7 @@ to when .I x is negative infinity. - +.PP Before glibc 2.19, .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6810 the glibc implementation of these functions did not set @@ -195,7 +195,7 @@ to .B ERANGE on an underflow range error. .I x - +.PP .\" In glibc versions 2.3.3 and earlier, an argument of +0 or \-0 incorrectly produced a domain error diff --git a/man3/timeradd.3 b/man3/timeradd.3 index e8662d8401..ac780e1f5d 100644 --- a/man3/timeradd.3 +++ b/man3/timeradd.3 @@ -82,7 +82,7 @@ pointed to by The result is normalized such that .I res\->tv_usec has a value in the range 0 to 999,999. - +.PP .BR timersub () subtracts the time value in .I b @@ -95,21 +95,21 @@ pointed to by The result is normalized such that .I res\->tv_usec has a value in the range 0 to 999,999. - +.PP .BR timerclear () zeros out the .I timeval structure pointed to by .IR tvp , so that it represents the Epoch: 1970-01-01 00:00:00 +0000 (UTC). - +.PP .BR timerisset () returns true (nonzero) if either field of the .I timeval structure pointed to by .I tvp contains a nonzero value. - +.PP .BR timercmp () compares the timer values in .I a @@ -136,7 +136,7 @@ and .I == do not work; portable applications can instead use - +.PP !timercmp(..., <) !timercmp(..., >) !timercmp(..., !=) diff --git a/man3/tmpnam.3 b/man3/tmpnam.3 index 3ae06889ff..2b9ce3c6f4 100644 --- a/man3/tmpnam.3 +++ b/man3/tmpnam.3 @@ -60,7 +60,7 @@ avoid using these functions; use or .BR tmpfile (3) instead. - +.PP The .BR tmpnam () function returns a pointer to a string that is a valid filename, @@ -94,7 +94,7 @@ are defined in just like the .B TMP_MAX mentioned below.) - +.PP The .BR tmpnam_r () function performs the same task as @@ -128,7 +128,7 @@ SVr4, 4.3BSD, C89, C99, POSIX.1-2001. POSIX.1-2008 marks .BR tmpnam () as obsolete. - +.PP .BR tmpnam_r () is a nonstandard extension that is also available .\" Appears to be on Solaris diff --git a/man3/toupper.3 b/man3/toupper.3 index 3bcd498d04..7f241a66da 100644 --- a/man3/toupper.3 +++ b/man3/toupper.3 @@ -59,7 +59,7 @@ _GNU_SOURCE .PD .SH DESCRIPTION These functions convert lowercase letters to uppercase, and vice versa. - +.PP If .I c is a lowercase letter, @@ -73,7 +73,7 @@ The function performs the same task, but uses the locale referred to by the locale handle .IR locale . - +.PP If .I c is an uppercase letter, @@ -96,7 +96,7 @@ value nor .BR EOF , the behavior of these functions is undefined. - +.PP The behavior of .BR toupper_l () and @@ -132,7 +132,7 @@ T} Thread safety MT-Safe .BR toupper (), .BR tolower (): C89, C99, 4.3BSD, POSIX.1-2001, POSIX.1-2008. - +.PP .BR toupper_l (), .BR tolower_l (): POSIX.1-2008. @@ -150,7 +150,7 @@ is of type it must be cast to .IR "unsigned char" , as in the following example: - +.PP .nf .in +4n char c; @@ -158,7 +158,7 @@ char c; res = toupper((unsigned char) c); .in .fi - +.PP This is necessary because .I char may be the equivalent @@ -168,7 +168,7 @@ converting to .IR int , yielding a value that is outside the range of .IR "unsigned char" . - +.PP The details of what constitutes an uppercase or lowercase letter depend on the locale. For example, the default diff --git a/man3/towlower.3 b/man3/towlower.3 index 576712d638..db8d21d647 100644 --- a/man3/towlower.3 +++ b/man3/towlower.3 @@ -57,7 +57,7 @@ it returns the lowercase equivalent of In all other cases, .I wc is returned unchanged. - +.PP The .BR towlower_l () function performs the same task, @@ -73,7 +73,7 @@ is the special locale object (see .BR duplocale (3)) or is not a valid locale object handle. - +.PP The argument .I wc must be representable as a @@ -111,7 +111,7 @@ T} Thread safety MT-Safe .BR towlower (): C99, POSIX.1-2001 (XSI); present as an XSI extension in POSIX.1-2008, but marked obsolete. - +.PP .BR towlower_l (): POSIX.1-2008. .SH NOTES diff --git a/man3/towupper.3 b/man3/towupper.3 index 8acf5fe96c..4109744f1e 100644 --- a/man3/towupper.3 +++ b/man3/towupper.3 @@ -57,7 +57,7 @@ it returns the uppercase equivalent of In all other cases, .I wc is returned unchanged. - +.PP The .BR towupper_l () function performs the same task, @@ -73,7 +73,7 @@ is the special locale object (see .BR duplocale (3)) or is not a valid locale object handle. - +.PP The argument .I wc must be representable as a @@ -111,7 +111,7 @@ T} Thread safety MT-Safe .BR towupper (): C99, POSIX.1-2001 (XSI); present as an XSI extension in POSIX.1-2008, but marked obsolete. - +.PP .BR towupper_l (): POSIX.1-2008. .SH NOTES diff --git a/man3/trunc.3 b/man3/trunc.3 index eeb26947b2..6e29822e26 100644 --- a/man3/trunc.3 +++ b/man3/trunc.3 @@ -58,7 +58,7 @@ to the nearest integer not larger in absolute value. .SH RETURN VALUE These functions return the rounded integer value. - +.PP If .IR x is integral, infinite, or NaN, diff --git a/man3/tzset.3 b/man3/tzset.3 index dc3cc0f543..2ceef94234 100644 --- a/man3/tzset.3 +++ b/man3/tzset.3 @@ -147,7 +147,7 @@ Day 0 is a Sunday. The \fItime\fP fields specify when, in the local time currently in effect, the change to the other time occurs. If omitted, the default is 02:00:00. - +.PP Here is an example for New Zealand, where the standard time (NZST) is 12 hours ahead of UTC, and daylight saving time (NZDT), 13 hours ahead of UTC, diff --git a/man3/ualarm.3 b/man3/ualarm.3 index 5154ba2b6b..973e75043f 100644 --- a/man3/ualarm.3 +++ b/man3/ualarm.3 @@ -116,7 +116,7 @@ argument is 0. .\" This case is not documented in HP-US, Solar, FreeBSD, NetBSD, or OpenBSD! On Linux (and probably most other systems), the effect is to cancel any pending alarm. - +.PP The type .I useconds_t is an unsigned integer type capable of holding integers diff --git a/man3/ulimit.3 b/man3/ulimit.3 index 5288841de3..48ed1c2bd5 100644 --- a/man3/ulimit.3 +++ b/man3/ulimit.3 @@ -43,7 +43,7 @@ For the shell command .BR ulimit (), see .BR bash (1). - +.PP The .BR ulimit () call will get or set some limit for the calling process. @@ -87,7 +87,7 @@ T{ .BR ulimit () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO SVr4, POSIX.1-2001. POSIX.1-2008 marks diff --git a/man3/undocumented.3 b/man3/undocumented.3 index a891efcb91..3d07727e71 100644 --- a/man3/undocumented.3 +++ b/man3/undocumented.3 @@ -42,7 +42,7 @@ similar to that of the other Linux section 3 man pages), and send it to .B mtk.manpages@gmail.com for inclusion in the next man page release. .SS The list - +.PP .BR authdes_create (3), .BR authdes_getucred (3), .BR authdes_pk_create (3), diff --git a/man3/unlocked_stdio.3 b/man3/unlocked_stdio.3 index ec5fc9a3dc..8308577d48 100644 --- a/man3/unlocked_stdio.3 +++ b/man3/unlocked_stdio.3 @@ -161,7 +161,7 @@ The four functions .BR putc_unlocked (), .BR putchar_unlocked () are in POSIX.1-2001 and POSIX.1-2008. - +.PP The nonstandard .BR *_unlocked () variants occur on a few UNIX systems, and are available in recent glibc. diff --git a/man3/updwtmp.3 b/man3/updwtmp.3 index aa06ab4ad3..48ba242e09 100644 --- a/man3/updwtmp.3 +++ b/man3/updwtmp.3 @@ -73,7 +73,7 @@ T{ .BR logwtmp () T} Thread safety MT-Unsafe sig:ALRM timer .TE - +.sp 1 .SH CONFORMING TO Not in POSIX.1. Present on Solaris, NetBSD, and perhaps other systems. diff --git a/man3/uselocale.3 b/man3/uselocale.3 index c19ff94016..2da947e2b5 100644 --- a/man3/uselocale.3 +++ b/man3/uselocale.3 @@ -59,7 +59,7 @@ After a successful call to any calls by this thread to functions that depend on the locale will operate as though the locale has been set to .IR newloc . - +.PP The .I newloc argument can have one of the following values: diff --git a/man3/usleep.3 b/man3/usleep.3 index 289caf7419..d2a95e35f5 100644 --- a/man3/usleep.3 +++ b/man3/usleep.3 @@ -106,14 +106,14 @@ POSIX.1-2001 declares this function obsolete; use instead. POSIX.1-2008 removes the specification of .BR usleep (). - +.PP On the original BSD implementation, and in glibc before version 2.2.2, the return type of this function is .IR void . The POSIX version returns .IR int , and this is also the prototype used since glibc 2.2.2. - +.PP Only the .B EINVAL error return is documented by SUSv2 and POSIX.1-2001. diff --git a/man3/wcrtomb.3 b/man3/wcrtomb.3 index a76195ae36..72b2869c1d 100644 --- a/man3/wcrtomb.3 +++ b/man3/wcrtomb.3 @@ -77,9 +77,9 @@ In this case, .I wc is ignored, and the function effectively returns - +.PP wcrtomb(buf, L\(aq\\0\(aq, ps) - +.PP where .I buf is an internal anonymous buffer. @@ -118,7 +118,7 @@ T{ .BR wcrtomb () T} Thread safety MT-Unsafe race:wcrtomb/!ps .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/wcsdup.3 b/man3/wcsdup.3 index 762bb2bd37..2dda89745a 100644 --- a/man3/wcsdup.3 +++ b/man3/wcsdup.3 @@ -79,7 +79,7 @@ T{ .BR wcsdup () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008. This function is not specified in POSIX.1-2001, diff --git a/man3/wcsnrtombs.3 b/man3/wcsnrtombs.3 index 22977696d5..3ee6e90b4c 100644 --- a/man3/wcsnrtombs.3 +++ b/man3/wcsnrtombs.3 @@ -169,7 +169,7 @@ T{ .BR wcsnrtombs () T} Thread safety MT-Unsafe race:wcsnrtombs/!ps .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2008. .SH NOTES diff --git a/man3/wcsrtombs.3 b/man3/wcsrtombs.3 index bc34f6bd57..f7ae91be90 100644 --- a/man3/wcsrtombs.3 +++ b/man3/wcsrtombs.3 @@ -135,7 +135,7 @@ T{ .BR wcsrtombs () T} Thread safety MT-Unsafe race:wcsrtombs/!ps .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/wcstombs.3 b/man3/wcstombs.3 index 6e9bbbaa1b..c4a757deab 100644 --- a/man3/wcstombs.3 +++ b/man3/wcstombs.3 @@ -99,7 +99,7 @@ T{ .BR wcstombs () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/wctob.3 b/man3/wctob.3 index fd08588b02..8acb568c7d 100644 --- a/man3/wctob.3 +++ b/man3/wctob.3 @@ -59,7 +59,7 @@ T{ .BR wctob () T} Thread safety MT-Safe .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/wcwidth.3 b/man3/wcwidth.3 index 1d8443c3b2..8217589407 100644 --- a/man3/wcwidth.3 +++ b/man3/wcwidth.3 @@ -56,7 +56,7 @@ T} Thread safety MT-Safe locale .TE .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. - +.PP Note that glibc before 2.2.5 used the prototype .br .nf diff --git a/man3/wordexp.3 b/man3/wordexp.3 index 1e6c783ec7..5189206d73 100644 --- a/man3/wordexp.3 +++ b/man3/wordexp.3 @@ -203,7 +203,7 @@ T{ .BR wordfree () T} Thread safety MT-Safe .TE - +.sp 1 In the above table, .I utent in diff --git a/man3/wprintf.3 b/man3/wprintf.3 index b3126d6655..310489b393 100644 --- a/man3/wprintf.3 +++ b/man3/wprintf.3 @@ -224,7 +224,7 @@ T{ .BR vswprintf () T} Thread safety MT-Safe locale .TE - +.sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C99. .SH NOTES diff --git a/man3/xcrypt.3 b/man3/xcrypt.3 index b99d75137d..22556dfb20 100644 --- a/man3/xcrypt.3 +++ b/man3/xcrypt.3 @@ -80,7 +80,7 @@ T{ .BR xdecrypt () T} Thread safety MT-Safe .TE - +.sp 1 .SH BUGS The prototypes are missing from the abovementioned include file. .SH SEE ALSO diff --git a/man3/xdr.3 b/man3/xdr.3 index f7c03c284a..87dc013449 100644 --- a/man3/xdr.3 +++ b/man3/xdr.3 @@ -606,7 +606,7 @@ T{ .BR xdr_wrapstring () T} Thread safety MT-Safe .TE - +.sp 1 .SH SEE ALSO .BR rpc (3) .LP @@ -131,11 +131,11 @@ values. On success, these functions return the appropriate Bessel value of the second kind for .IR x . - +.PP If .I x is a NaN, a NaN is returned. - +.PP If .I x is negative, @@ -147,7 +147,7 @@ or .RB - HUGE_VALL , respectively. (POSIX.1-2001 also allows a NaN return for this case.) - +.PP If .I x is 0.0, @@ -158,11 +158,11 @@ and the functions return or .RB - HUGE_VALL , respectively. - +.PP If the result underflows, a range error occurs, and the functions return 0.0 - +.PP If the result overflows, a range error occurs, and the functions return @@ -271,7 +271,7 @@ instead of as POSIX.1-2004 requires. .\" FIXME . .\" Bug raised: http://sourceware.org/bugzilla/show_bug.cgi?id=6807 - +.PP In glibc version 2.3.2 and earlier, .\" FIXME . Actually, 2.3.2 is the earliest test result I have; so yet .\" to confirm if this error occurs only in 2.3.2. |