diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-08-18 01:12:54 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-08-18 01:12:54 +0200 |
| commit | dd3568a14752868cd4c71257c19f47d62e84fcb1 (patch) | |
| tree | 5c2c1b2452313c20891e090e5bcf9678e4ed7786 | |
| parent | 37d5e699477a69de48e3df7e9909b1c768cfeec9 (diff) | |
| download | man-pages-dd3568a14752868cd4c71257c19f47d62e84fcb1.tar.gz | |
getent.1, intro.1, time.1, _exit.2, alloc_hugepages.2, arch_prctl.2, clock_getres.2, getitimer.2, getrusage.2, intro.2, ioctl_console.2, ioctl_list.2, ioctl_tty.2, kill.2, madvise.2, mlock.2, mmap.2, mount.2, open.2, outb.2, perf_event_open.2, ptrace.2, quotactl.2, reboot.2, recv.2, remap_file_pages.2, select.2, semctl.2, send.2, set_tid_address.2, seteuid.2, shmop.2, statfs.2, times.2, truncate.2, uname.2, uselib.2, vm86.2, wait.2, a64l.3, aio_cancel.3, aio_fsync.3, aio_read.3, aio_return.3, aio_suspend.3, aio_write.3, alloca.3, argz_add.3, atexit.3, basename.3, bindresvport.3, cacos.3, cacosh.3, carg.3, casin.3, casinh.3, catan.3, catanh.3, catgets.3, catopen.3, cexp.3, cfree.3, cimag.3, clog.3, conj.3, creal.3, ctime.3, des_crypt.3, dirfd.3, div.3, dlopen.3, envz_add.3, exit.3, fenv.3, flockfile.3, fmtmsg.3, fpclassify.3, fpurge.3, fseeko.3, ftime.3, ftok.3, ftw.3, getcontext.3, getcwd.3, getdate.3, getfsent.3, getgrent.3, getgrnam.3, gethostbyname.3, getipnodebyname.3, getlogin.3, getpwnam.3, getrpcent.3, getspnam.3, getutent.3, gsignal.3, hsearch.3, lockf.3, logb.3, login.3, lseek64.3, makecontext.3, malloc.3, malloc_hook.3, nan.3, nl_langinfo.3, openpty.3, posix_spawn.3, putenv.3, realpath.3, remainder.3, rint.3, rpc.3, rtime.3, scandir.3, setlogmask.3, shm_open.3, sigpause.3, statvfs.3, stdio_ext.3, strfmon.3, strftime.3, strptime.3, strtod.3, strtol.3, strtoul.3, swab.3, sysconf.3, syslog.3, tcgetpgrp.3, tempnam.3, termios.3, tmpfile.3, tmpnam.3, ttyslot.3, tzset.3, ualarm.3, usleep.3, wordexp.3, xcrypt.3, xdr.3, cciss.4, console_codes.4, full.4, hd.4, loop.4, mem.4, null.4, pts.4, ram.4, random.4, tty.4, ttyS.4, vcs.4, networks.5, nsswitch.conf.5, protocols.5, resolv.conf.5, slabinfo.5, termcap.5, ascii.7, boot.7, bootparam.7, charsets.7, icmp.7, inode.7, man.7, netdevice.7, posixoptions.7, ld.so.8: srcfix: use .PP instead of .LP
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
170 files changed, 752 insertions, 752 deletions
diff --git a/man1/getent.1 b/man1/getent.1 index a1a49fd46e..0af76e824a 100644 --- a/man1/getent.1 +++ b/man1/getent.1 @@ -42,7 +42,7 @@ Otherwise, if no .I key is provided, all entries will be displayed (unless the database does not support enumeration). -.LP +.PP The .I database may be any of those supported by the GNU C Library, listed below: diff --git a/man1/intro.1 b/man1/intro.1 index 3587f1101c..a2e3ee3087 100644 --- a/man1/intro.1 +++ b/man1/intro.1 @@ -33,7 +33,7 @@ web browsers, file and image viewers and editors, and so on. Linux is a flavor of UNIX, and as a first approximation all user commands under UNIX work precisely the same under Linux (and FreeBSD and lots of other UNIX-like systems). -.LP +.PP Under Linux, there are GUIs (graphical user interfaces), where you can point and click and drag, and hopefully get work done without first reading lots of documentation. @@ -72,9 +72,9 @@ See also .BR dash (1), .BR ksh (1), .BR zsh (1). -.LP +.PP A session might go like: -.LP +.PP .RS .nf .RB "knuth login: " aeb @@ -118,9 +118,9 @@ maja 0501\-1136285 $ .fi .RE -.LP +.PP Here typing Control-D ended the session. -.LP +.PP The .B $ here was the command prompt\(emit is the shell's way of indicating @@ -130,13 +130,13 @@ in lots of ways, and one might include stuff like username, machine name, current directory, time, and so on. An assignment PS1="What next, master? " would change the prompt as indicated. -.LP +.PP We see that there are commands .I date (that gives date and time), and .I cal (that gives a calendar). -.LP +.PP The command .I ls lists the contents of the current directory\(emit tells you what @@ -152,7 +152,7 @@ Owner and permissions can be changed by the commands .I chown and .IR chmod . -.LP +.PP The command .I cat will show the contents of a file. @@ -162,26 +162,26 @@ parameters are concatenated and sent to "standard output" .BR stdout (3)), here the terminal screen.) -.LP +.PP The command .I cp (from "copy") will copy a file. -.LP +.PP The command .I mv (from "move"), on the other hand, only renames it. -.LP +.PP The command .I diff lists the differences between two files. Here there was no output because there were no differences. -.LP +.PP The command .I rm (from "remove") deletes the file, and be careful! it is gone. No wastepaper basket or anything. Deleted means lost. -.LP +.PP The command .I grep (from "g/re/p") finds occurrences of a string in one or more files. @@ -205,15 +205,15 @@ to .I tel when the current directory is .IR /home/aeb . -.LP +.PP The command .I pwd prints the current directory. -.LP +.PP The command .I cd changes the current directory. -.LP +.PP Try alternatively .I cd and @@ -225,11 +225,11 @@ usage: "cd", "cd .", "cd ..", "cd /" and "cd ~". The command .I mkdir makes a new directory. -.LP +.PP The command .I rmdir removes a directory if it is empty, and complains otherwise. -.LP +.PP The command .I find (with a rather baroque syntax) will find files with given name @@ -286,7 +286,7 @@ sends the text through some usually .IR less . Hit the space bar to get the next page, hit q to quit. -.LP +.PP In documentation it is customary to refer to man pages by giving the name and section number, as in .BR man (1). @@ -294,12 +294,12 @@ Man pages are terse, and allow you to find quickly some forgotten detail. For newcomers an introductory text with more examples and explanations is useful. -.LP +.PP A lot of GNU/FSF software is provided with info files. Type "info info" for an introduction on the use of the program .IR info . -.LP +.PP Special topics are often treated in HOWTOs. Look in .I /usr/share/doc/howto/en diff --git a/man1/time.1 b/man1/time.1 index 3ec2334f92..1df692e049 100644 --- a/man1/time.1 +++ b/man1/time.1 @@ -100,7 +100,7 @@ using the option or the .B TIME environment variable. -.LP +.PP The default format string is: .PP .in +4n @@ -109,7 +109,7 @@ The default format string is: %Iinputs+%Ooutputs (%Fmajor+%Rminor)pagefaults %Wswaps .EE .in -.LP +.PP When the .I \-p option is given, the (portable) output format is used: @@ -135,7 +135,7 @@ The conversions follow. All of those used by .BR tcsh (1) are supported. -.LP +.PP .B "Time" .TP .B %E @@ -154,7 +154,7 @@ Total number of CPU-seconds that the process spent in user mode. .TP .B %P Percentage of the CPU that this job got, computed as (%U + %S) / %E. -.LP +.PP .B "Memory" .TP .B %M @@ -207,7 +207,7 @@ Number of times the process was context-switched involuntarily .B %w Number of waits: times that the program was context-switched voluntarily, for instance while waiting for an I/O operation to complete. -.LP +.PP .B "I/O" .TP .B %I @@ -268,10 +268,10 @@ Not all resources are measured by all versions of UNIX, so some of the values might be reported as zero. The present selection was mostly inspired by the data provided by 4.2 or 4.3BSD. -.LP +.PP GNU time version 1.7 is not yet localized. Thus, it does not implement the POSIX requirements. -.LP +.PP The environment variable .B TIME was badly chosen. @@ -283,14 +283,14 @@ to use environment variables with the name of a utility to override the utility to be used. Uses like MORE or TIME for options to programs (instead of program pathnames) tend to lead to difficulties. -.LP +.PP It seems unfortunate that .I \-o overwrites instead of appends. (That is, the .I \-a option should be the default.) -.LP +.PP Mail suggestions and bug reports for GNU .B time to diff --git a/man2/_exit.2 b/man2/_exit.2 index 59d2cae5f4..c55d2a612c 100644 --- a/man2/_exit.2 +++ b/man2/_exit.2 @@ -63,14 +63,14 @@ operation). The process's parent is sent a .B SIGCHLD signal. -.LP +.PP The value .I "status & 0377" is returned to the parent process as the process's exit status, and can be collected using one of the .BR wait (2) family of calls. -.LP +.PP The function .BR _Exit () is equivalent to @@ -86,7 +86,7 @@ was introduced by C99. For a discussion on the effects of an exit, the transmission of exit status, zombie processes, signals sent, and so on, see .BR exit (3). -.LP +.PP The function .BR _exit () is like diff --git a/man2/alloc_hugepages.2 b/man2/alloc_hugepages.2 index def9eabc0f..1e8d3659dd 100644 --- a/man2/alloc_hugepages.2 +++ b/man2/alloc_hugepages.2 @@ -46,7 +46,7 @@ They existed only on i386 and ia64 (when built with In Linux 2.4.20, the syscall numbers exist, but the calls fail with the error .BR ENOSYS . -.LP +.PP On i386 the memory management hardware knows about ordinary pages (4 KiB) and huge pages (2 or 4 MiB). Similarly ia64 knows about huge pages of @@ -54,7 +54,7 @@ several sizes. These system calls serve to map huge pages into the process's memory or to free them again. Huge pages are locked into memory, and are not swapped. -.LP +.PP The .I key argument is an identifier. @@ -63,7 +63,7 @@ not inherited by children. When positive the pages are shared with other applications using the same .IR key , and inherited by child processes. -.LP +.PP The .I addr argument of @@ -78,12 +78,12 @@ argument of .BR alloc_hugepages () is a hint, that the kernel may or may not follow. Addresses must be properly aligned. -.LP +.PP The .I len argument is the length of the required segment. It must be a multiple of the huge page size. -.LP +.PP The .I prot argument specifies the memory protection of the segment. @@ -91,7 +91,7 @@ It is one of .BR PROT_READ , .BR PROT_WRITE , .BR PROT_EXEC . -.LP +.PP The .I flag argument is ignored, unless @@ -123,7 +123,7 @@ The system call is not supported on this kernel. .I /proc/sys/vm/nr_hugepages Number of configured hugetlb pages. This can be read and written. -.LP +.PP .I /proc/meminfo Gives info on the number of configured hugetlb pages and on their size in the three variables HugePages_Total, HugePages_Free, Hugepagesize. @@ -138,7 +138,7 @@ Memory backed by huge pages (if the CPU supports them) is obtained by using .BR mmap (2) to map files in this virtual filesystem. -.LP +.PP The maximal number of huge pages can be specified using the .B hugepages= boot parameter. diff --git a/man2/arch_prctl.2 b/man2/arch_prctl.2 index 1cadede612..83da76db29 100644 --- a/man2/arch_prctl.2 +++ b/man2/arch_prctl.2 @@ -48,7 +48,7 @@ is interpreted as either an for the "set" operations, or as an .IR "unsigned long\ *" , for the "get" operations. -.LP +.PP Subfunctions for x86-64 are: .TP .B ARCH_SET_FS diff --git a/man2/clock_getres.2 b/man2/clock_getres.2 index 5488e5319b..5078be1c4e 100644 --- a/man2/clock_getres.2 +++ b/man2/clock_getres.2 @@ -104,18 +104,18 @@ The argument is the identifier of the particular clock on which to act. A clock may be system-wide and hence visible for all processes, or per-process if it measures time only within a single process. -.LP +.PP All implementations support the system-wide real-time clock, which is identified by .BR CLOCK_REALTIME . Its time represents seconds and nanoseconds since the Epoch. When its time is changed, timers for a relative interval are unaffected, but timers for an absolute point in time are affected. -.LP +.PP More clocks may be implemented. The interpretation of the corresponding time values and the effect on timers is unspecified. -.LP +.PP Sufficiently recent versions of glibc and the Linux kernel support the following clocks: .TP diff --git a/man2/getitimer.2 b/man2/getitimer.2 index 7d44d442f5..f61199d02f 100644 --- a/man2/getitimer.2 +++ b/man2/getitimer.2 @@ -61,7 +61,7 @@ In conjunction with .BR ITIMER_VIRTUAL , this timer can be used to profile user and system CPU time consumed by the process. -.LP +.PP A process has only one of each of the three types of timers. .PP Timer values are defined by the following structures: diff --git a/man2/getrusage.2 b/man2/getrusage.2 index fadea98742..96c6d96ff6 100644 --- a/man2/getrusage.2 +++ b/man2/getrusage.2 @@ -246,7 +246,7 @@ although POSIX.1-2001 explicitly prohibits this. This nonconformance is rectified in Linux 2.6.9 and later. .\" See the description of getrusage() in XSH. .\" A similar statement was also in SUSv2. -.LP +.PP The structure definition shown at the start of this page was taken from 4.3BSD Reno. .PP diff --git a/man2/intro.2 b/man2/intro.2 index ea9a84c6ce..e9c1de9d29 100644 --- a/man2/intro.2 +++ b/man2/intro.2 @@ -52,7 +52,7 @@ setting .I errno if the system call returns an error number when the kernel returns the CPU to user mode. -.LP +.PP However, in a few cases, a wrapper function may do rather more than this, for example, performing some preprocessing of the arguments before trapping to kernel mode, diff --git a/man2/ioctl_console.2 b/man2/ioctl_console.2 index 72cb8fa47c..231cde8b67 100644 --- a/man2/ioctl_console.2 +++ b/man2/ioctl_console.2 @@ -71,7 +71,7 @@ unsigned long integer in However, if a higher order bit is set, the LEDs revert to normal: displaying the state of the keyboard functions of caps lock, num lock, and scroll lock. -.LP +.PP Before Linux 1.1.54, the LEDs just reflected the state of the corresponding keyboard flags, and KDGETLED/KDSETLED would also change the keyboard flags. diff --git a/man2/ioctl_list.2 b/man2/ioctl_list.2 index 5150d5652d..5f4065f61a 100644 --- a/man2/ioctl_list.2 +++ b/man2/ioctl_list.2 @@ -58,7 +58,7 @@ This list is very incomplete. Ioctl command values are 32-bit constants. In principle these constants are completely arbitrary, but people have tried to build some structure into them. -.LP +.PP The old Linux situation was that of mostly 16-bit constants, where the last byte is a serial number, and the preceding byte(s) give a type indicating the driver. @@ -77,7 +77,7 @@ has value .B CYGETTIMEOUT has value 0x00435906, with 0x43 0x59 = \(aqC\(aq \(aqY\(aq indicating the cyclades driver. -.LP +.PP Later (0.98p5) some more information was built into the number. One has 2 direction bits (00: none, 01: write, 10: read, 11: read/write) @@ -85,7 +85,7 @@ followed by 14 size bits (giving the size of the argument), followed by an 8-bit type (collecting the ioctls in groups for a common purpose or a common driver), and an 8-bit serial number. -.LP +.PP The macros describing this structure live in .I <asm/ioctl.h> and are @@ -96,12 +96,12 @@ They use .I sizeof(size) so that size is a misnomer here: this third argument is a data type. -.LP +.PP Note that the size bits are very unreliable: in lots of cases they are wrong, either because of buggy macros using .IR sizeof(sizeof(struct)) , or because of legacy values. -.LP +.PP Thus, it seems that the new structure only gave disadvantages: it does not help in checking, but it causes varying values for the various architectures. diff --git a/man2/ioctl_tty.2 b/man2/ioctl_tty.2 index f8cfd34272..b06b939f23 100644 --- a/man2/ioctl_tty.2 +++ b/man2/ioctl_tty.2 @@ -20,7 +20,7 @@ Most require a third argument, of varying type, here called .I argp or .IR arg . -.LP +.PP Use of .I ioctl makes for nonportable programs. @@ -54,7 +54,7 @@ Equivalent to .br Allow the output buffer to drain, discard pending input, and set the current serial port settings. -.LP +.PP The following four ioctls are just like .BR TCGETS , .BR TCSETS , @@ -107,7 +107,7 @@ Get window size. .TP .BI "TIOCSWINSZ const struct winsize *" argp Set window size. -.LP +.PP The struct used by these ioctls is defined as .PP .in +4n @@ -422,7 +422,7 @@ Clear the indicated modem bits. .TP .BI "TIOCMBIS const int *" argp Set the indicated modem bits. -.LP +.PP The following bits are used by the above ioctls: .PP .nf @@ -477,7 +477,7 @@ Set the CLOCAL flag in the structure when .RI * argp is nonzero, and clear it otherwise. -.LP +.PP If the .B CLOCAL flag for a line is off, the hardware carrier detect (DCD) diff --git a/man2/kill.2 b/man2/kill.2 index 580fa9b694..f647843100 100644 --- a/man2/kill.2 +++ b/man2/kill.2 @@ -128,13 +128,13 @@ process, are those for which has explicitly installed signal handlers. This is done to assure the system is not brought down accidentally. -.LP +.PP POSIX.1 requires that \fIkill(\-1,sig)\fP send \fIsig\fP to all processes that the calling process may send signals to, except possibly for some implementation-defined system processes. Linux allows a process to signal itself, but on Linux the call \fIkill(\-1,sig)\fP does not signal the calling process. -.LP +.PP POSIX.1 requires that if a process sends a signal to itself, and the sending thread does not have the signal blocked, and no other thread diff --git a/man2/madvise.2 b/man2/madvise.2 index d5db4ab4ba..80cb63b403 100644 --- a/man2/madvise.2 +++ b/man2/madvise.2 @@ -99,7 +99,7 @@ values listed here have analogs in the POSIX-specified .BR posix_madvise (3) function, and the values have the same meanings, with the exception of .BR MADV_DONTNEED . -.LP +.PP The advice is indicated in the .I advice argument, which is one of the following: diff --git a/man2/mlock.2 b/man2/mlock.2 index 3800a22173..baeff7394e 100644 --- a/man2/mlock.2 +++ b/man2/mlock.2 @@ -212,7 +212,7 @@ The caller is not privileged, but needs privilege .RB ( CAP_IPC_LOCK ) to perform the requested operation. .\"SVr4 documents an additional EAGAIN error code. -.LP +.PP For .BR mlock (), .BR mlock2 (), @@ -246,13 +246,13 @@ exceeding the allowed maximum. (For example, unlocking a range in the middle of a currently locked mapping would result in three mappings: two locked mappings at each end and an unlocked mapping in the middle.) -.LP +.PP For .BR mlock2 (): .TP .B EINVAL Unknown \fIflags\fP were specified. -.LP +.PP For .BR mlockall (): .TP @@ -263,7 +263,7 @@ was specified without either .B MCL_FUTURE or .BR MCL_CURRENT . -.LP +.PP For .BR munlockall (): .TP diff --git a/man2/mmap.2 b/man2/mmap.2 index 48e7680f3a..943c050cf5 100644 --- a/man2/mmap.2 +++ b/man2/mmap.2 @@ -86,7 +86,7 @@ in the file (or other object) referred to by the file descriptor .I offset must be a multiple of the page size as returned by .IR sysconf(_SC_PAGE_SIZE) . -.LP +.PP The .I prot argument describes the desired memory protection of the mapping @@ -106,7 +106,7 @@ Pages may be written. .TP .B PROT_NONE Pages may not be accessed. -.LP +.PP The .I flags argument determines whether updates to the mapping @@ -133,7 +133,7 @@ the underlying file. It is unspecified whether changes made to the file after the .BR mmap () call are visible in the mapped region. -.LP +.PP Both of these flags are described in POSIX.1-2001 and POSIX.1-2008. .PP In addition, zero or more of the following values can be ORed in @@ -352,7 +352,7 @@ option. Because of the security implications, that option is normally enabled only on embedded devices (i.e., devices where one has complete control of the contents of user memory). -.LP +.PP Of the above flags, only .B MAP_FIXED is specified in POSIX.1-2001 and POSIX.1-2008. @@ -364,13 +364,13 @@ However, most systems also support .\" POSIX may add MAP_ANON in the future .\" http://austingroupbugs.net/tag_view_page.php?tag_id=8 .\" http://austingroupbugs.net/view.php?id=850 -.LP +.PP Memory mapped by .BR mmap () is preserved across .BR fork (2), with the same attributes. -.LP +.PP A file is mapped in multiples of the page size. For a file that is not a multiple of the page size, the remaining memory is zeroed when mapped, @@ -388,7 +388,7 @@ The region is also automatically unmapped when the process is terminated. On the other hand, closing the file descriptor does not unmap the region. -.LP +.PP The address .I addr must be a multiple of the page size (but @@ -523,7 +523,7 @@ The operation was prevented by a file seal; see was set but the object specified by .I fd is open for writing. -.LP +.PP Use of a mapped region can result in these signals: .TP .B SIGSEGV @@ -637,7 +637,7 @@ field for the mapped file may be updated at any time between the .BR mmap () and the corresponding unmapping; the first reference to a mapped page will update the field if it has not been already. -.LP +.PP The .I st_ctime and diff --git a/man2/mount.2 b/man2/mount.2 index 9f4a856e83..87cb1a9b82 100644 --- a/man2/mount.2 +++ b/man2/mount.2 @@ -737,7 +737,7 @@ in 1.1.69 when a different .B MS_SYNC was added to \fI<mman.h>\fP. -.LP +.PP Before Linux 2.4 an attempt to execute a set-user-ID or set-group-ID program on a filesystem mounted with .B MS_NOSUID diff --git a/man2/open.2 b/man2/open.2 index 3aa637746d..597e6fc5f8 100644 --- a/man2/open.2 +++ b/man2/open.2 @@ -1166,7 +1166,7 @@ but does not necessarily have the intention to read or write. This is typically used to open devices in order to get a file descriptor for use with .BR ioctl (2). -.LP +.PP The (undefined) effect of .B O_RDONLY | O_TRUNC varies among implementations. @@ -1490,7 +1490,7 @@ but less efficiently.) .\" .\" .SS O_DIRECT -.LP +.PP The .B O_DIRECT flag may impose alignment restrictions on the length and address @@ -1506,7 +1506,7 @@ for doing so, for example the .B XFS_IOC_DIOINFO operation in .BR xfsctl (3). -.LP +.PP Under Linux 2.4, transfer sizes, and the alignment of the user buffer and the file offset must all be multiples of the logical block size of the filesystem. @@ -1554,7 +1554,7 @@ with ensuring that it will not be available to the child after .BR fork (2). -.LP +.PP The .B O_DIRECT flag was introduced in SGI IRIX, where it has alignment @@ -1564,7 +1564,7 @@ IRIX has also a call to query appropriate alignments, and sizes. FreeBSD 4.x introduced a flag of the same name, but without alignment restrictions. -.LP +.PP .B O_DIRECT support was added under Linux in kernel version 2.4.10. Older Linux kernels simply ignore this flag. @@ -1573,7 +1573,7 @@ Some filesystems may not implement the flag and will fail with .B EINVAL if it is used. -.LP +.PP Applications should avoid mixing .B O_DIRECT and normal I/O to the same file, @@ -1584,7 +1584,7 @@ using either mode alone. Likewise, applications should avoid mixing .BR mmap (2) of files with direct I/O to the same files. -.LP +.PP The behavior of .B O_DIRECT with NFS will differ from local filesystems. diff --git a/man2/outb.2 b/man2/outb.2 index b8aa80ea02..3e1b03cb4f 100644 --- a/man2/outb.2 +++ b/man2/outb.2 @@ -64,7 +64,7 @@ This family of functions is used to do low-level port input and output. The out* functions do port output, the in* functions do port input; the b-suffix functions are byte-width and the w-suffix functions word-width; the _p-suffix functions pause until the I/O completes. -.LP +.PP They are primarily designed for internal kernel use, but can be used from user space. .\" , given the following information diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index 3bce742c61..27c4072375 100644 --- a/man2/perf_event_open.2 +++ b/man2/perf_event_open.2 @@ -1174,7 +1174,7 @@ Count when we read or write the memory location. .TP .BR HW_BREAKPOINT_X Count when we execute code at the memory location. -.LP +.PP The values can be combined via a bitwise or, but the combination of .B HW_BREAKPOINT_R diff --git a/man2/ptrace.2 b/man2/ptrace.2 index 73f459ef02..6c3245d9b2 100644 --- a/man2/ptrace.2 +++ b/man2/ptrace.2 @@ -120,7 +120,7 @@ may observe and control the execution of another process (the "tracee"), and examine and change the tracee's memory and registers. It is primarily used to implement breakpoint debugging and system call tracing. -.LP +.PP A tracee first needs to be attached to the tracer. Attachment and subsequent commands are per thread: in a multithreaded process, @@ -137,13 +137,13 @@ a specific tracee using a call of the form where .I pid is the thread ID of the corresponding Linux thread. -.LP +.PP (Note that in this page, a "multithreaded process" means a thread group consisting of threads created using the .BR clone (2) .B CLONE_THREAD flag.) -.LP +.PP A process can initiate a trace by calling .BR fork (2) and having the resulting child do a @@ -154,7 +154,7 @@ Alternatively, one process may commence tracing another process using .B PTRACE_ATTACH or .BR PTRACE_SEIZE . -.LP +.PP While being traced, the tracee will stop each time a signal is delivered, even if the signal is being ignored. (An exception is @@ -171,7 +171,7 @@ the tracer can use various ptrace requests to inspect and modify the tracee. The tracer then causes the tracee to continue, optionally ignoring the delivered signal (or even delivering a different signal instead). -.LP +.PP If the .B PTRACE_O_TRACEEXEC option is not in effect, all successful calls to @@ -181,11 +181,11 @@ by the traced process will cause it to be sent a signal, giving the parent a chance to gain control before the new program begins execution. -.LP +.PP When the tracer is finished tracing, it can cause the tracee to continue executing in a normal, untraced mode via .BR PTRACE_DETACH . -.LP +.PP The value of .I request determines the action to be performed: @@ -1017,7 +1017,7 @@ all threads exit. Tracees report their death to their tracer(s). Notification of this event is delivered via .BR waitpid (2). -.LP +.PP Note that the killing signal will first cause signal-delivery-stop (on one tracee only), and only after it is injected by the tracer @@ -1026,7 +1026,7 @@ will death from the signal happen on .I all tracees within a multithreaded process. (The term "signal-delivery-stop" is explained below.) -.LP +.PP .B SIGKILL does not generate signal-delivery-stop and therefore the tracer can't suppress it. @@ -1038,16 +1038,16 @@ The net effect is that .B SIGKILL always kills the process (all its threads), even if some threads of the process are ptraced. -.LP +.PP When the tracee calls .BR _exit (2), it reports its death to its tracer. Other threads are not affected. -.LP +.PP When any thread executes .BR exit_group (2), every tracee in its thread group reports its death to its tracer. -.LP +.PP If the .B PTRACE_O_TRACEEXIT option is on, @@ -1062,7 +1062,7 @@ depending on the kernel version; see BUGS below), and when threads are torn down on .BR execve (2) in a multithreaded process. -.LP +.PP The tracer cannot assume that the ptrace-stopped tracee exists. There are many scenarios when the tracee may die while stopped (such as .BR SIGKILL ). @@ -1087,7 +1087,7 @@ ptrace operation returned may return 0 instead. In other words, the tracee may be "not yet fully dead", but already refusing ptrace requests. -.LP +.PP The tracer can't assume that the tracee .I always ends its life by reporting @@ -1123,11 +1123,11 @@ in group-stop before it will not respond to signals until .B SIGCONT is received. -.LP +.PP There are many kinds of states when the tracee is stopped, and in ptrace discussions they are often conflated. Therefore, it is important to use precise terms. -.LP +.PP In this manual page, any stopped state in which the tracee is ready to accept ptrace commands from the tracer is called .IR ptrace-stop . @@ -1139,14 +1139,14 @@ be further subdivided into .IR PTRACE_EVENT stops, and so on. These stopped states are described in detail below. -.LP +.PP When the running tracee enters ptrace-stop, it notifies its tracer using .BR waitpid (2) (or one of the other "wait" system calls). Most of this manual page assumes that the tracer waits with: -.LP +.PP pid = waitpid(pid_or_minus_1, &status, __WALL); -.LP +.PP Ptrace-stopped tracees are reported as returns with .I pid greater than 0 and @@ -1158,7 +1158,7 @@ true. .\" rules different if user wants to use waitid? Will waitid require .\" WEXITED? .\" -.LP +.PP The .B __WALL flag does not include the @@ -1166,14 +1166,14 @@ flag does not include the and .B WEXITED flags, but implies their functionality. -.LP +.PP Setting the .B WCONTINUED flag when calling .BR waitpid (2) is not recommended: the "continued" state is per-process and consuming it can confuse the real parent of the tracee. -.LP +.PP Use of the .B WNOHANG flag may cause @@ -1194,7 +1194,7 @@ Example: .\" FIXME . .\" waitid usage? WNOWAIT? .\" describe how wait notifications queue (or not queue) -.LP +.PP The following kinds of ptrace-stops exist: signal-delivery-stops, group-stops, .B PTRACE_EVENT @@ -1233,7 +1233,7 @@ signal-delivery-stop doesn't happen until the signal is unblocked, with the usual exception that .B SIGSTOP can't be blocked. -.LP +.PP Signal-delivery-stop is observed by the tracer as .BR waitpid (2) returning with @@ -1250,9 +1250,9 @@ returns a stopping signal, this may be a group-stop; see below. .SS Signal injection and suppression After signal-delivery-stop is observed by the tracer, the tracer should restart the tracee with the call -.LP +.PP ptrace(PTRACE_restart, pid, 0, sig) -.LP +.PP where .B PTRACE_restart is one of the restarting ptrace requests. @@ -1265,13 +1265,13 @@ is delivered. This operation is called .I "signal injection" in this manual page, to distinguish it from signal-delivery-stop. -.LP +.PP The .I sig value may be different from the .I WSTOPSIG(status) value: the tracer can cause a different signal to be injected. -.LP +.PP Note that a suppressed signal still causes system calls to return prematurely. In this case, system calls will be restarted: the tracer will @@ -1287,7 +1287,7 @@ signal is suppressed; however, kernel bugs exist which cause some system calls to fail with .B EINTR even though no observable signal is injected to the tracee. -.LP +.PP Restarting ptrace commands issued in ptrace-stops other than signal-delivery-stop are not guaranteed to inject a signal, even if .I sig @@ -1298,7 +1298,7 @@ may simply be ignored. Ptrace users should not try to "create a new signal" this way: use .BR tgkill (2) instead. -.LP +.PP The fact that signal injection requests may be ignored when restarting the tracee after ptrace stops that are not signal-delivery-stops @@ -1313,7 +1313,7 @@ with the intention of injecting but .I stopsig gets ignored and the tracee continues to run. -.LP +.PP The .B SIGCONT signal has a side effect of waking up (all threads of) @@ -1333,11 +1333,11 @@ was delivered. In other words, .B SIGCONT may be not the first signal observed by the tracee after it was sent. -.LP +.PP Stopping signals cause (all threads of) a process to enter group-stop. This side effect happens after signal injection, and therefore can be suppressed by the tracer. -.LP +.PP In Linux 2.4 and earlier, the .B SIGSTOP signal can't be injected. @@ -1347,7 +1347,7 @@ signal can't be injected. .\" /* The debugger continued. Ignore SIGSTOP. */ .\" if (signr == SIGSTOP) .\" continue; -.LP +.PP .B PTRACE_GETSIGINFO can be used to retrieve a .I siginfo_t @@ -1376,7 +1376,7 @@ will group-stop be initiated on tracees within the multithreaded process. As usual, every tracee reports its group-stop separately to the corresponding tracer. -.LP +.PP Group-stop is observed by the tracer as .BR waitpid (2) returning with @@ -1385,9 +1385,9 @@ true, with the stopping signal available via .IR WSTOPSIG(status) . The same result is returned by some other classes of ptrace-stops, therefore the recommended practice is to perform the call -.LP +.PP ptrace(PTRACE_GETSIGINFO, pid, 0, &siginfo) -.LP +.PP The call can be avoided if the signal is not .BR SIGSTOP , .BR SIGTSTP , @@ -1408,7 +1408,7 @@ then it is definitely a group-stop. ("no such process") if a .B SIGKILL killed the tracee.) -.LP +.PP If tracee was attached using .BR PTRACE_SEIZE , group-stop is indicated by @@ -1418,7 +1418,7 @@ This allows detection of group-stops without requiring an extra .B PTRACE_GETSIGINFO call. -.LP +.PP As of Linux 2.6.38, after the tracer sees the tracee ptrace-stop and until it restarts or kills it, the tracee will not run, @@ -1427,7 +1427,7 @@ and will not send notifications (except death) to the tracer, even if the tracer enters into another .BR waitpid (2) call. -.LP +.PP The kernel behavior described in the previous paragraph causes a problem with transparent handling of stopping signals. If the tracer restarts the tracee after group-stop, @@ -1441,7 +1441,7 @@ signals will not be reported to the tracer; this would cause the .B SIGCONT signals to have no effect on the tracee. -.LP +.PP Since Linux 3.4, there is a method to overcome this problem: instead of .BR PTRACE_CONT , a @@ -1458,7 +1458,7 @@ If the tracer sets options, the tracee will enter ptrace-stops called .B PTRACE_EVENT stops. -.LP +.PP .B PTRACE_EVENT stops are observed by the tracer as .BR waitpid (2) @@ -1511,7 +1511,7 @@ with the .B CLONE_VFORK flag, but after the child unblocked this tracee by exiting or execing. -.LP +.PP For all four stops described above, the stop occurs in the parent (i.e., the tracee), not in the newly created thread. @@ -1560,7 +1560,7 @@ portion of the seccomp filter rule) can be retrieved with .BR PTRACE_GETEVENTMSG . The semantics of this stop are described in detail in a separate section below. -.LP +.PP .B PTRACE_GETSIGINFO on .B PTRACE_EVENT @@ -1599,7 +1599,7 @@ Note that all mentions .BR PTRACE_SYSEMU apply equally to .BR PTRACE_SYSEMU_SINGLESTEP. -.LP +.PP However, even if the tracee was continued using .BR PTRACE_SYSCALL , it is not guaranteed that the next stop will be a syscall-exit-stop. @@ -1616,7 +1616,7 @@ or die silently (if it is a thread group leader, the happened in another thread, and that thread is not traced by the same tracer; this situation is discussed later). -.LP +.PP Syscall-enter-stop and syscall-exit-stop are observed by the tracer as .BR waitpid (2) returning with @@ -1631,7 +1631,7 @@ option was set by the tracer, then .I WSTOPSIG(status) will give the value .IR "(SIGTRAP\ |\ 0x80)" . -.LP +.PP Syscall-stops can be distinguished from signal-delivery-stop with .B SIGTRAP by querying @@ -1656,12 +1656,12 @@ was sent by the kernel. .TP .IR si_code " == SIGTRAP or " si_code " == (SIGTRAP|0x80)" This is a syscall-stop. -.LP +.PP However, syscall-stops happen very often (twice per system call), and performing .B PTRACE_GETSIGINFO for every syscall-stop may be somewhat expensive. -.LP +.PP Some architectures allow the cases to be distinguished by examining registers. For example, on x86, @@ -1684,13 +1684,13 @@ looks like "syscall-stop which is not syscall-enter-stop"; in other words, it looks like a "stray syscall-exit-stop" and can be detected this way. But such detection is fragile and is best avoided. -.LP +.PP Using the .B PTRACE_O_TRACESYSGOOD option is the recommended method to distinguish syscall-stops from other kinds of ptrace-stops, since it is reliable and does not incur a performance penalty. -.LP +.PP Syscall-enter-stop and syscall-exit-stop are indistinguishable from each other by the tracer. The tracer needs to keep track of the sequence of @@ -1705,12 +1705,12 @@ However, note that seccomp stops (see below) can cause syscall-exit-stops, without preceding syscall-entry-stops. If seccomp is in use, care needs to be taken not to misinterpret such stops as syscall-entry-stops. -.LP +.PP If after syscall-enter-stop, the tracer uses a restarting command other than .BR PTRACE_SYSCALL , syscall-exit-stop is not generated. -.LP +.PP .B PTRACE_GETSIGINFO on syscall-stops returns .B SIGTRAP @@ -1809,12 +1809,12 @@ and .BR PTRACE_KILL ) require the tracee to be in a ptrace-stop, otherwise they fail with .BR ESRCH . -.LP +.PP When the tracee is in ptrace-stop, the tracer can read and write data to the tracee using informational commands. These commands leave the tracee in ptrace-stopped state: -.LP +.PP .nf ptrace(PTRACE_PEEKTEXT/PEEKDATA/PEEKUSER, pid, addr, 0); ptrace(PTRACE_POKETEXT/POKEDATA/POKEUSER, pid, addr, long_val); @@ -1827,7 +1827,7 @@ These commands leave the tracee in ptrace-stopped state: ptrace(PTRACE_GETEVENTMSG, pid, 0, &long_var); ptrace(PTRACE_SETOPTIONS, pid, 0, PTRACE_O_flags); .fi -.LP +.PP Note that some errors are not reported. For example, setting signal information .RI ( siginfo ) @@ -1838,7 +1838,7 @@ querying .B PTRACE_GETEVENTMSG may succeed and return some random value if current ptrace-stop is not documented as returning a meaningful event message. -.LP +.PP The call .PP ptrace(PTRACE_SETOPTIONS, pid, 0, PTRACE_O_flags); @@ -1851,12 +1851,12 @@ Flags are inherited by new tracees created and "auto-attached" via active or .BR PTRACE_O_TRACECLONE options. -.LP +.PP Another group of commands makes the ptrace-stopped tracee run. They have the form: -.LP +.PP ptrace(cmd, pid, 0, sig); -.LP +.PP where .I cmd is @@ -1909,14 +1909,14 @@ may race and the concurrent may be lost. .\" .\" FIXME Describe how to attach to a thread which is already group-stopped. -.LP +.PP Since attaching sends .B SIGSTOP and the tracer usually suppresses it, this may cause a stray .B EINTR return from the currently executing system call in the tracee, as described in the "Signal injection and suppression" section. -.LP +.PP Since Linux 3.4, .B PTRACE_SEIZE can be used instead of @@ -1928,7 +1928,7 @@ it after attach (or at any other time) without sending it any signals, use .B PTRACE_INTERRUPT command. -.LP +.PP The request .PP ptrace(PTRACE_TRACEME, 0, 0, 0); @@ -1943,7 +1943,7 @@ with .PP and allow the parent (which is our tracer now) to observe our signal-delivery-stop. -.LP +.PP If the .BR PTRACE_O_TRACEFORK , .BR PTRACE_O_TRACEVFORK , @@ -1967,7 +1967,7 @@ are automatically attached to the same tracer which traced their parent. .B SIGSTOP is delivered to the children, causing them to enter signal-delivery-stop after they exit the system call which created them. -.LP +.PP Detaching of the tracee is performed by: .PP ptrace(PTRACE_DETACH, pid, 0, sig); @@ -1979,7 +1979,7 @@ If the tracee is in signal-delivery-stop, a signal can be injected. Otherwise, the .I sig parameter may be silently ignored. -.LP +.PP If the tracee is running when the tracer wants to detach it, the usual solution is to send .B SIGSTOP @@ -2003,7 +2003,7 @@ because no signal delivery happens while it is\(emnot even .BR SIGSTOP . .\" FIXME Describe how to detach from a group-stopped tracee so that it .\" doesn't run, but continues to wait for SIGCONT. -.LP +.PP If the tracer dies, all tracees are automatically detached and restarted, unless they were in group-stop. Handling of restart from group-stop is currently buggy, @@ -2075,10 +2075,10 @@ If the thread group leader was not traced .BR execve (2) it will appear as if it has become a tracee of the tracer of the execing tracee. -.LP +.PP All of the above effects are the artifacts of the thread ID change in the tracee. -.LP +.PP The .B PTRACE_O_TRACEEXEC option is the recommended tool for dealing with this situation. @@ -2098,13 +2098,13 @@ option disables legacy .B SIGTRAP generation on .BR execve (2). -.LP +.PP When the tracer receives .B PTRACE_EVENT_EXEC stop notification, it is guaranteed that except this tracee and the thread group leader, no other threads from the process are alive. -.LP +.PP On receiving the .B PTRACE_EVENT_EXEC stop notification, @@ -2114,11 +2114,11 @@ and retain only one data structure\(emone which describes the single still running tracee, with .PP thread ID == thread group ID == process ID. -.LP +.PP Example: two threads call .BR execve (2) at the same time: -.LP +.PP .nf *** we get syscall-enter-stop in thread 1: ** PID1 execve("/bin/foo", "foo" <unfinished ...> @@ -2130,7 +2130,7 @@ PID2 execve("/bin/bar", "bar" <unfinished ...> *** we get syscall-exit-stop for PID0: ** PID0 <... execve resumed> ) = 0 .fi -.LP +.PP If the .B PTRACE_O_TRACEEXEC option is @@ -2157,7 +2157,7 @@ set to 0 .RI ( SI_USER ). This signal may be blocked by signal mask, and thus may be delivered (much) later. -.LP +.PP Usually, the tracer (for example, .BR strace (1)) would not want to show this extra post-execve @@ -2185,10 +2185,10 @@ This used to cause the real parent of the process to stop receiving several kinds of .BR waitpid (2) notifications when the child process is traced by some other process. -.LP +.PP Many of these bugs have been fixed, but as of Linux 2.6.38 several still exist; see BUGS below. -.LP +.PP As of Linux 2.6.38, the following is believed to work correctly: .IP * 3 exit/death by signal is reported first to the tracer, then, @@ -2203,7 +2203,7 @@ On success, the .B PTRACE_PEEK* requests return the requested data (but see NOTES), while other requests return zero. -.LP +.PP On error, all requests return \-1, and .I errno is set appropriately. @@ -2273,25 +2273,25 @@ setting unused/ignored arguments to .I 0L or .IR "(void\ *)\ 0". -.LP +.PP In Linux kernels before 2.6.26, .\" See commit 00cd5c37afd5f431ac186dd131705048c0a11fdb .BR init (1), the process with PID 1, may not be traced. -.LP +.PP A tracees parent continues to be the tracer even if that tracer calls .BR execve (2). -.LP +.PP The layout of the contents of memory and the USER area are quite operating-system- and architecture-specific. The offset supplied, and the data returned, might not entirely match with the definition of .IR "struct user" . .\" See http://lkml.org/lkml/2008/5/8/375 -.LP +.PP The size of a "word" is determined by the operating-system variant (e.g., for 32-bit Linux it is 32 bits). -.LP +.PP This page documents the way the .BR ptrace () call works currently in Linux. @@ -2651,10 +2651,10 @@ This can be worked around by redefining to .BR PTRACE_OLDSETOPTIONS , if that is defined. -.LP +.PP Group-stop notifications are sent to the tracer, but not to real parent. Last confirmed on 2.6.38.6. -.LP +.PP If a thread group leader is traced and exits by calling .BR _exit (2), .\" Note from Denys Vlasenko: @@ -2685,7 +2685,7 @@ One possible workaround is to the thread group leader instead of restarting it in this case. Last confirmed on 2.6.38.6. .\" FIXME . need to test/verify this scenario -.LP +.PP A .B SIGKILL signal may still cause a @@ -2695,7 +2695,7 @@ This may be changed in the future; .B SIGKILL is meant to always immediately kill tasks even under ptrace. Last confirmed on Linux 3.13. -.LP +.PP Some system calls return with .B EINTR if a signal was sent to a tracee, but delivery was suppressed by the tracer. diff --git a/man2/quotactl.2 b/man2/quotactl.2 index 525e75ab4d..73ac899d8e 100644 --- a/man2/quotactl.2 +++ b/man2/quotactl.2 @@ -31,12 +31,12 @@ quotactl \- manipulate disk quotas .nf .B #include <sys/quota.h> .B #include <xfs/xqm.h> /* for XFS quotas */ -.LP +.PP .BI "int quotactl(int " cmd ", const char *" special ", int " id \ ", caddr_t " addr ); .fi .SH DESCRIPTION -.LP +.PP The quota system can be used to set per-user, per-group, and per-project limits on the amount of disk space used on a filesystem. For each user and/or group, @@ -672,7 +672,7 @@ The .IR special ", " id " and " addr arguments are ignored. .SH RETURN VALUE -.LP +.PP On success, .BR quotactl () returns 0; on error \-1 diff --git a/man2/reboot.2 b/man2/reboot.2 index 17a3db3eed..d4c1030dce 100644 --- a/man2/reboot.2 +++ b/man2/reboot.2 @@ -153,10 +153,10 @@ data will be lost. The system is suspended (hibernated) to disk. This option is available only if the kernel was configured with .BR CONFIG_HIBERNATION . -.LP +.PP Only the superuser may call .BR reboot (). -.LP +.PP The precise effect of the above actions depends on the architecture. For the i386 architecture, the additional argument does not do anything at present (2.1.122), but the type of reboot can be diff --git a/man2/recv.2 b/man2/recv.2 index 35717597ca..baff6067da 100644 --- a/man2/recv.2 +++ b/man2/recv.2 @@ -498,7 +498,7 @@ does not refer to a socket. .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, 4.4BSD (these interfaces first appeared in 4.2BSD). -.LP +.PP POSIX.1 describes only the .BR MSG_OOB , .BR MSG_PEEK , diff --git a/man2/remap_file_pages.2 b/man2/remap_file_pages.2 index 06af8fad3f..1a18cf3d60 100644 --- a/man2/remap_file_pages.2 +++ b/man2/remap_file_pages.2 @@ -80,7 +80,7 @@ to rearrange the correspondence between the pages of the mapping and the pages of the file. It is possible to map the same page of a file into multiple locations within the mapped region. -.LP +.PP The .I pgoff and diff --git a/man2/select.2 b/man2/select.2 index 0b1a1314e5..001915c543 100644 --- a/man2/select.2 +++ b/man2/select.2 @@ -452,7 +452,7 @@ and .I suseconds_t are defined in .IR <sys/types.h> . -.LP +.PP Concerning prototypes, the classical situation is that one should include .I <time.h> diff --git a/man2/semctl.2 b/man2/semctl.2 index 057c286d29..dbd2a054eb 100644 --- a/man2/semctl.2 +++ b/man2/semctl.2 @@ -377,7 +377,7 @@ as for .B SEM_STAT the identifier of the semaphore set whose index was given in .IR semid . -.LP +.PP All other .I cmd values return 0 on success. @@ -496,7 +496,7 @@ program to provide information on allocated resources. In the future these may modified or moved to a .I /proc filesystem interface. -.LP +.PP Various fields in a \fIstruct semid_ds\fP were typed as .I short under Linux 2.2 @@ -528,7 +528,7 @@ call: Maximum value for .BR semval : implementation dependent (32767). -.LP +.PP For greater portability, it is best to always call .BR semctl () with four arguments. diff --git a/man2/send.2 b/man2/send.2 index 13fe1d76be..2a754f22d3 100644 --- a/man2/send.2 +++ b/man2/send.2 @@ -420,7 +420,7 @@ is set. .SH CONFORMING TO 4.4BSD, SVr4, POSIX.1-2001. These interfaces first appeared in 4.2BSD. -.LP +.PP POSIX.1-2001 describes only the .B MSG_OOB and diff --git a/man2/set_tid_address.2 b/man2/set_tid_address.2 index 915a812398..e26c529a44 100644 --- a/man2/set_tid_address.2 +++ b/man2/set_tid_address.2 @@ -67,14 +67,14 @@ flag, is set to the value passed in the .I ctid argument of that system call. -.LP +.PP The system call .BR set_tid_address () sets the .I clear_child_tid value for the calling thread to .IR tidptr . -.LP +.PP When a thread whose .I clear_child_tid is not NULL terminates, then, diff --git a/man2/seteuid.2 b/man2/seteuid.2 index f6fed9e25c..83c8fd7c8c 100644 --- a/man2/seteuid.2 +++ b/man2/seteuid.2 @@ -108,7 +108,7 @@ saved set-user-ID (saved set-group-ID) is possible since Linux 1.1.37 (1.1.38). On an arbitrary system one should check .BR _POSIX_SAVED_IDS . -.LP +.PP Under glibc 2.0 .BI seteuid( euid ) is equivalent to diff --git a/man2/shmop.2 b/man2/shmop.2 index ff3cc25c73..3f9d2b70c8 100644 --- a/man2/shmop.2 +++ b/man2/shmop.2 @@ -270,7 +270,7 @@ On Linux, it is possible to attach a shared memory segment even if it is already marked to be deleted. However, POSIX.1 does not specify this behavior and many other implementations do not support it. -.LP +.PP The following system parameter affects .BR shmat (): .TP diff --git a/man2/statfs.2 b/man2/statfs.2 index ba469a10ff..c50ea0284f 100644 --- a/man2/statfs.2 +++ b/man2/statfs.2 @@ -363,7 +363,7 @@ Several operating systems restrict giving out the field to the superuser only (and zero it for unprivileged users), because this field is used in the filehandle of the filesystem when NFS-exported, and giving it out is a security concern. -.LP +.PP Under some operating systems, the .I fsid can be used as the second argument to the diff --git a/man2/times.2 b/man2/times.2 index b8b0905b43..832df36e2a 100644 --- a/man2/times.2 +++ b/man2/times.2 @@ -64,7 +64,7 @@ struct tms { }; .EE .in -.LP +.PP The .I tms_utime field contains the CPU time spent executing instructions @@ -87,7 +87,7 @@ field contains the sum of the and .I tms_cstime values for all waited-for terminated children. -.LP +.PP Times for terminated children (and their descendants) are added in at the moment .BR wait (2) @@ -96,7 +96,7 @@ or returns their process ID. In particular, times of grandchildren that the children did not wait for are never seen. -.LP +.PP All times reported are in clock ticks. .SH RETURN VALUE .BR times () @@ -155,7 +155,7 @@ just returns a function result. However, POSIX does not specify this behavior, and most other UNIX implementations require a non-NULL value for .IR buf . -.LP +.PP Note that .BR clock (3) also returns a value of type diff --git a/man2/truncate.2 b/man2/truncate.2 index 2799f9813b..cbce67986a 100644 --- a/man2/truncate.2 +++ b/man2/truncate.2 @@ -87,20 +87,20 @@ or referenced by to be truncated to a size of precisely .I length bytes. -.LP +.PP If the file previously was larger than this size, the extra data is lost. If the file previously was shorter, it is extended, and the extended part reads as null bytes (\(aq\\0\(aq). -.LP +.PP The file offset is not changed. -.LP +.PP If the size changed, then the st_ctime and st_mtime fields (respectively, time of last status change and time of last modification; see .BR inode (7)) for the file are updated, and the set-user-ID and set-group-ID mode bits may be cleared. -.LP +.PP With .BR ftruncate (), the file must be open for writing; with diff --git a/man2/uname.2 b/man2/uname.2 index c55a102656..225e1aacc8 100644 --- a/man2/uname.2 +++ b/man2/uname.2 @@ -95,7 +95,7 @@ about such things, so it has to be told what to answer here. The same holds for the additional .I domainname field. -.LP +.PP To this end, Linux uses the system calls .BR sethostname (2) and @@ -113,7 +113,7 @@ The same holds for and the .I domainname field. -.LP +.PP The length of the fields in the struct varies. Some operating systems or libraries use a hardcoded 9 or 33 or 65 or 257. @@ -128,7 +128,7 @@ or Clearly, it is a bad idea to use any of these constants; just use sizeof(...). Often 257 is chosen in order to have room for an internet hostname. -.LP +.PP Part of the utsname information is also accessible via .IR /proc/sys/kernel/ { ostype , .IR hostname , @@ -136,7 +136,7 @@ Part of the utsname information is also accessible via .IR version , .IR domainname }. .SS C library/kernel differences -.LP +.PP Over time, increases in the size of the .I utsname structure have led to three successive versions of diff --git a/man2/uselib.2 b/man2/uselib.2 index 625d075ef9..ed8afe1d96 100644 --- a/man2/uselib.2 +++ b/man2/uselib.2 @@ -94,7 +94,7 @@ In ancient libc versions, was used to load the shared libraries with names found in an array of names in the binary. -.LP +.PP .\" libc 4.3.1f - changelog 1993-03-02 Since libc 4.3.2, startup code tries to prefix these names with "/usr/lib", "/lib" and "" before giving up. @@ -104,12 +104,12 @@ found in .BR LD_LIBRARY_PATH , and if not found there, prefixes "/usr/lib", "/lib" and "/" are tried. -.LP +.PP From libc 4.4.4 on only the library "/lib/ld.so" is loaded, so that this dynamic library can load the remaining libraries needed (again using this call). This is also the state of affairs in libc5. -.LP +.PP glibc2 does not use this call. .PP Since Linux 3.15, diff --git a/man2/vm86.2 b/man2/vm86.2 index 8b91192f16..3317af1b01 100644 --- a/man2/vm86.2 +++ b/man2/vm86.2 @@ -45,7 +45,7 @@ The definition of .IR "struct vm86_struct" was changed in 1.1.8 and 1.1.9. -.LP +.PP These calls cause the process to enter VM86 mode (virtual-8086 in Intel literature), and are used by .BR dosemu . diff --git a/man2/wait.2 b/man2/wait.2 index 2b144f6ba3..f50a8a665c 100644 --- a/man2/wait.2 +++ b/man2/wait.2 @@ -504,7 +504,7 @@ of another thread, even when the latter belongs to the same thread group. However, POSIX prescribes such functionality, and since Linux 2.4 a thread can, and by default will, wait on children of other threads in the same thread group. -.LP +.PP The following Linux-specific .I options are for use with children created using diff --git a/man3/a64l.3 b/man3/a64l.3 index fb825a0f25..6e01a0b5e9 100644 --- a/man3/a64l.3 +++ b/man3/a64l.3 @@ -48,7 +48,7 @@ uses only the low order 32 bits of and .BR a64l () sign-extends its 32-bit result. -.LP +.PP The 64 digits in the base-64 system are: .RS .nf @@ -84,7 +84,7 @@ The value returned by .BR l64a () may be a pointer to a static buffer, possibly overwritten by later calls. -.LP +.PP The behavior of .BR l64a () is undefined when @@ -93,10 +93,10 @@ is negative. If .I value is zero, it returns an empty string. -.LP +.PP These functions are broken in glibc before 2.2.5 (puts most significant digit first). -.LP +.PP This is not the encoding used by .BR uuencode (1). .SH SEE ALSO diff --git a/man3/aio_cancel.3 b/man3/aio_cancel.3 index 2152fcbf8d..4897c1a0cb 100644 --- a/man3/aio_cancel.3 +++ b/man3/aio_cancel.3 @@ -48,7 +48,7 @@ is canceled. for a description of the .I aiocb structure.) -.LP +.PP Normal asynchronous notification occurs for canceled requests (see .BR aio (7) and @@ -60,21 +60,21 @@ is set to \-1, and the request error status is set to .BR ECANCELED . The control block of requests that cannot be canceled is not changed. -.LP +.PP If the request could not be canceled, then it will terminate in the usual way after performing the I/O operation. (In this case, .BR aio_error (3) will return the status .BR EINPROGRESSS .) -.LP +.PP If .I aiocbp is not NULL, and .I fd differs from the file descriptor with which the asynchronous operation was initiated, unspecified results occur. -.LP +.PP Which operations are cancelable is implementation-defined. .\" FreeBSD: not those on raw disk devices. .SH RETURN VALUE diff --git a/man3/aio_fsync.3 b/man3/aio_fsync.3 index 251e73ec99..d028de9dce 100644 --- a/man3/aio_fsync.3 +++ b/man3/aio_fsync.3 @@ -41,7 +41,7 @@ associated with for a description of the .I aiocb structure.) -.LP +.PP More precisely, if .I op is @@ -57,7 +57,7 @@ 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 +.PP Apart from .IR aio_fildes , the only field in the structure pointed to by diff --git a/man3/aio_read.3 b/man3/aio_read.3 index bf6a02981d..4b7ba537cd 100644 --- a/man3/aio_read.3 +++ b/man3/aio_read.3 @@ -53,13 +53,13 @@ of the structure pointed to by for a description of the .I aiocb structure.) -.LP +.PP The data is read starting at the absolute position .IR aiocbp\->aio_offset , regardless of the file offset. After the call, the value of the file offset is unspecified. -.LP +.PP The "asynchronous" means that this call returns as soon as the request has been enqueued; the read may or may not have completed when the call returns. @@ -72,18 +72,18 @@ Asynchronous notification of I/O completion can be obtained by setting appropriately; see .BR sigevent (7) for details. -.LP +.PP If .B _POSIX_PRIORITIZED_IO is defined, and this file supports it, then the asynchronous operation is submitted at a priority equal to that of the calling process minus .IR aiocbp\->aio_reqprio . -.LP +.PP The field .I aiocbp\->aio_lio_opcode is ignored. -.LP +.PP No data is read from a regular file beyond its maximum offset. .SH RETURN VALUE On success, 0 is returned. diff --git a/man3/aio_return.3 b/man3/aio_return.3 index e066aa38d0..e2cb7ed7cd 100644 --- a/man3/aio_return.3 +++ b/man3/aio_return.3 @@ -41,7 +41,7 @@ with control block pointed to by for a description of the .I aiocb structure.) -.LP +.PP This function should be called only once for any given request, after .BR aio_error (3) returns something other than diff --git a/man3/aio_suspend.3 b/man3/aio_suspend.3 index c0343abe9b..6297714f89 100644 --- a/man3/aio_suspend.3 +++ b/man3/aio_suspend.3 @@ -53,7 +53,7 @@ is not NULL and the specified time interval has passed. .I timespec structure, see .BR nanosleep (2).) -.LP +.PP The .I nitems argument specifies the number of items in @@ -71,7 +71,7 @@ or for a description of the .I aiocb structure.) -.LP +.PP If .B CLOCK_MONOTONIC is supported, this clock is used to measure diff --git a/man3/aio_write.3 b/man3/aio_write.3 index 8bac39c49c..992ad14d65 100644 --- a/man3/aio_write.3 +++ b/man3/aio_write.3 @@ -53,7 +53,7 @@ of the structure pointed to by for a description of the .I aiocb structure.) -.LP +.PP If .B O_APPEND is not set, the data is written starting at the @@ -66,7 +66,7 @@ is set, data is written at the end of the file in the same order as .BR aio_write () calls are made. After the call, the value of the file offset is unspecified. -.LP +.PP The "asynchronous" means that this call returns as soon as the request has been enqueued; the write may or may not have completed when the call returns. @@ -79,18 +79,18 @@ Asynchronous notification of I/O completion can be obtained by setting appropriately; see .BR sigevent (7) for details. -.LP +.PP If .B _POSIX_PRIORITIZED_IO is defined, and this file supports it, then the asynchronous operation is submitted at a priority equal to that of the calling process minus .IR aiocbp\->aio_reqprio . -.LP +.PP The field .I aiocbp\->aio_lio_opcode is ignored. -.LP +.PP No data is written to a regular file beyond its maximum offset. .SH RETURN VALUE On success, 0 is returned. diff --git a/man3/alloca.3 b/man3/alloca.3 index 1b68f6ea2e..1e61c26822 100644 --- a/man3/alloca.3 +++ b/man3/alloca.3 @@ -141,11 +141,11 @@ and that contains the lines: .fi with messy consequences if one has a private version of this function. -.LP +.PP The fact that the code is inlined means that it is impossible to take the address of this function, or to change its behavior by linking with a different library. -.LP +.PP The inlined code often consists of a single instruction adjusting the stack pointer, and does not check for stack overflow. Thus, there is no NULL error return. diff --git a/man3/argz_add.3 b/man3/argz_add.3 index 62a0cc7084..36406f4530 100644 --- a/man3/argz_add.3 +++ b/man3/argz_add.3 @@ -50,12 +50,12 @@ argz_next, argz_replace, argz_stringify \- functions to handle an argz list .fi .SH DESCRIPTION These functions are glibc-specific. -.LP +.PP An argz vector is a pointer to a character buffer together with a length. The intended interpretation of the character buffer is an array of strings, where the strings are separated by null bytes (\(aq\\0\(aq). If the length is nonzero, the last byte of the buffer must be a null byte. -.LP +.PP These functions are for handling argz vectors. The pair (NULL,0) is an argz vector, and, conversely, argz vectors of length 0 must have null pointer. @@ -64,7 +64,7 @@ Allocation of nonempty argz vectors is done using so that .BR free (3) can be used to dispose of them again. -.LP +.PP .BR argz_add () adds the string .I str @@ -74,7 +74,7 @@ and updates .I *argz and .IR *argz_len . -.LP +.PP .BR argz_add_sep () is similar, but splits the string .I str @@ -82,7 +82,7 @@ into substrings separated by the delimiter .IR delim . For example, one might use this on a UNIX search path with delimiter \(aq:\(aq. -.LP +.PP .BR argz_append () appends the argz vector .RI ( buf ,\ buf_len ) @@ -96,12 +96,12 @@ and .I *argz_len will be increased by .IR buf_len .) -.LP +.PP .BR argz_count () counts the number of strings, that is, the number of null bytes (\(aq\\0\(aq), in .RI ( argz ,\ argz_len ). -.LP +.PP .BR argz_create () converts a UNIX-style argument vector .IR argv , @@ -109,7 +109,7 @@ terminated by .IR "(char\ *)\ 0" , into an argz vector .RI ( *argz ,\ *argz_len ). -.LP +.PP .BR argz_create_sep () converts the null-terminated string .I str @@ -117,7 +117,7 @@ into an argz vector .RI ( *argz ,\ *argz_len ) by breaking it up at every occurrence of the separator .IR sep . -.LP +.PP .BR argz_delete () removes the substring pointed to by .I entry @@ -127,7 +127,7 @@ and updates .I *argz and .IR *argz_len . -.LP +.PP .BR argz_extract () is the opposite of .BR argz_create (). @@ -142,7 +142,7 @@ The array must have room for .IR argz_count ( argz ", " argz_len ") + 1" pointers. -.LP +.PP .BR argz_insert () is the opposite of .BR argz_delete (). @@ -161,7 +161,7 @@ If is NULL, then .I entry will inserted at the end. -.LP +.PP .BR argz_next () is a function to step trough the argz vector. If @@ -170,7 +170,7 @@ is NULL, the first entry is returned. Otherwise, the entry following is returned. It returns NULL if there is no following entry. -.LP +.PP .BR argz_replace () replaces each occurrence of .I str @@ -182,7 +182,7 @@ If is non-NULL, .I *replace_count will be incremented by the number of replacements. -.LP +.PP .BR argz_stringify () is the opposite of .BR argz_create_sep (). diff --git a/man3/atexit.3 b/man3/atexit.3 index 6c1176f92e..7c1c33ff4b 100644 --- a/man3/atexit.3 +++ b/man3/atexit.3 @@ -54,14 +54,14 @@ 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 +.PP POSIX.1 requires that an implementation allow at least .\" POSIX.1-2001, POSIX.1-2008 .B ATEXIT_MAX (32) such functions to be registered. The actual limit supported by an implementation can be obtained using .BR sysconf (3). -.LP +.PP When a child process is created via .BR fork (2), it inherits copies of its parent's registrations. diff --git a/man3/basename.3 b/man3/basename.3 index a8e078ab59..d7167963af 100644 --- a/man3/basename.3 +++ b/man3/basename.3 @@ -39,7 +39,7 @@ basename, dirname \- parse pathname components Warning: there are two different functions .BR basename () - see below. -.LP +.PP The functions .BR dirname () and @@ -161,7 +161,7 @@ empty string when has a trailing slash, and in particular also when it is "/". There is no GNU version of .BR dirname (). -.LP +.PP With glibc, one gets the POSIX version of .BR basename () when diff --git a/man3/bindresvport.3 b/man3/bindresvport.3 index ef920fc71c..9834b901ac 100644 --- a/man3/bindresvport.3 +++ b/man3/bindresvport.3 @@ -34,11 +34,11 @@ bindresvport \- bind a socket to a privileged IP port .nf .B #include <sys/types.h> .B #include <netinet/in.h> -.LP +.PP .BI "int bindresvport(int " sockfd ", struct sockaddr_in *" sin ); .fi .SH DESCRIPTION -.LP +.PP .BR bindresvport () is used to bind the socket referred to by the file descriptor diff --git a/man3/cacos.3 b/man3/cacos.3 index 42dc851a31..22cf96e7ff 100644 --- a/man3/cacos.3 +++ b/man3/cacos.3 @@ -25,7 +25,7 @@ If \fIy\ =\ cacos(z)\fP, then \fIz\ =\ ccos(y)\fP. The real part of .I y is chosen in the interval [0,pi]. -.LP +.PP One has: .nf diff --git a/man3/cacosh.3 b/man3/cacosh.3 index 2a7e0ad07c..3a7e3a58e2 100644 --- a/man3/cacosh.3 +++ b/man3/cacosh.3 @@ -28,7 +28,7 @@ is chosen in the interval [\-pi,pi]. The real part of .I y is chosen nonnegative. -.LP +.PP One has: .nf diff --git a/man3/carg.3 b/man3/carg.3 index 3bcf22688b..97e5f3ce7c 100644 --- a/man3/carg.3 +++ b/man3/carg.3 @@ -33,7 +33,7 @@ where .IR "x\ =\ creal(z)" and .IR "y\ =\ cimag(z)" . -.LP +.PP Or one may use polar coordinates and gets .nf @@ -48,7 +48,7 @@ and .IR "a\ =\ carg(z)" is the "phase angle", the argument of .IR z . -.LP +.PP One has: .nf diff --git a/man3/casin.3 b/man3/casin.3 index 0adf5d3e63..37d96170a8 100644 --- a/man3/casin.3 +++ b/man3/casin.3 @@ -24,7 +24,7 @@ If \fIy\ =\ casin(z)\fP, then \fIz\ =\ csin(y)\fP. The real part of .I y is chosen in the interval [\-pi/2,pi/2]. -.LP +.PP One has: .nf diff --git a/man3/casinh.3 b/man3/casinh.3 index 809321b77c..d9c9cf0db6 100644 --- a/man3/casinh.3 +++ b/man3/casinh.3 @@ -24,7 +24,7 @@ If \fIy\ =\ casinh(z)\fP, then \fIz\ =\ csinh(y)\fP. The imaginary part of .I y is chosen in the interval [\-pi/2,pi/2]. -.LP +.PP One has: .nf diff --git a/man3/catan.3 b/man3/catan.3 index 458b398e16..5342444802 100644 --- a/man3/catan.3 +++ b/man3/catan.3 @@ -23,7 +23,7 @@ These functions calculate the complex arc tangent of .IR z . If \fIy\ =\ catan(z)\fP, then \fIz\ =\ ctan(y)\fP. The real part of y is chosen in the interval [\-pi/2,pi/2]. -.LP +.PP One has: .nf diff --git a/man3/catanh.3 b/man3/catanh.3 index a4ffd5c3a9..b904be8b2c 100644 --- a/man3/catanh.3 +++ b/man3/catanh.3 @@ -25,7 +25,7 @@ If \fIy\ =\ catanh(z)\fP, then \fIz\ =\ ctanh(y)\fP. The imaginary part of .I y is chosen in the interval [\-pi/2,pi/2]. -.LP +.PP One has: .nf diff --git a/man3/catgets.3 b/man3/catgets.3 index 7d1906546b..3f1f86c6ee 100644 --- a/man3/catgets.3 +++ b/man3/catgets.3 @@ -57,7 +57,7 @@ the application if it is to be saved or modified. The return string is always terminated with a null byte (\(aq\\0\(aq). .SH RETURN VALUE -.LP +.PP On success, .BR catgets () returns a pointer to an internal buffer area diff --git a/man3/catopen.3 b/man3/catopen.3 index 0019b6fc48..f005d70024 100644 --- a/man3/catopen.3 +++ b/man3/catopen.3 @@ -46,7 +46,7 @@ If a file descriptor is used to implement catalog descriptors, then the .B FD_CLOEXEC flag will be set. -.LP +.PP The argument .I name specifies the name of the message catalog to be opened. @@ -88,7 +88,7 @@ Changing the .B LC_MESSAGES part of the locale may invalidate open catalog descriptors. -.LP +.PP The .I flag argument to @@ -101,7 +101,7 @@ then it will use the current locale setting for Otherwise, it will use the .B LANG environment variable. -.LP +.PP The function .BR catclose () closes the message catalog identified by @@ -124,7 +124,7 @@ The possible error values include all possible values for the .BR open (2) call. -.LP +.PP The function .BR catclose () returns 0 on success, or \-1 on failure. diff --git a/man3/cexp.3 b/man3/cexp.3 index 4c535a2e32..a0892c093d 100644 --- a/man3/cexp.3 +++ b/man3/cexp.3 @@ -21,7 +21,7 @@ Link with \fI\-lm\fP. These functions calculate e (2.71828..., the base of natural logarithms) raised to the power of .IR z . -.LP +.PP One has: .nf diff --git a/man3/cfree.3 b/man3/cfree.3 index 896636a126..5bbd233fab 100644 --- a/man3/cfree.3 +++ b/man3/cfree.3 @@ -64,7 +64,7 @@ In glibc, the function is a synonym for .BR free (3), "added for compatibility with SunOS". -.LP +.PP Other systems have other functions with this name. The declaration is sometimes in .I <stdlib.h> @@ -75,7 +75,7 @@ Some SCO and Solaris versions have malloc libraries with a 3-argument .BR cfree (), apparently as an analog to .BR calloc (3). -.LP +.PP If you need it while porting something, add .PP .in +4n @@ -85,7 +85,7 @@ If you need it while porting something, add .in .PP to your file. -.LP +.PP A frequently asked question is "Can I use .BR free (3) to free memory allocated with @@ -94,7 +94,7 @@ or do I need .BR cfree ()?" Answer: use .BR free (3). -.LP +.PP An SCO manual writes: "The cfree routine is provided for compliance to the iBCSe2 standard and simply calls free. The num and size diff --git a/man3/cimag.3 b/man3/cimag.3 index 446e27de8a..a9c61d471e 100644 --- a/man3/cimag.3 +++ b/man3/cimag.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions return the imaginary part of the complex number .IR z . -.LP +.PP One has: .nf diff --git a/man3/clog.3 b/man3/clog.3 index 7904f27f06..e658446142 100644 --- a/man3/clog.3 +++ b/man3/clog.3 @@ -30,13 +30,13 @@ Thus, if \fIy\ =\ clog(z)\fP, then \fIz\ =\ cexp(y)\fP. The imaginary part of .I y is chosen in the interval [\-pi,pi]. -.LP +.PP One has: .nf clog(z) = log(cabs(z)) + I * carg(z) .fi -.LP +.PP Note that .I z close to zero will cause an overflow. diff --git a/man3/conj.3 b/man3/conj.3 index 2e8c25eaf3..f6758949b2 100644 --- a/man3/conj.3 +++ b/man3/conj.3 @@ -21,7 +21,7 @@ Link with \fI\-lm\fP. These functions return the complex conjugate value of .IR z . That is the value obtained by changing the sign of the imaginary part. -.LP +.PP One has: .nf diff --git a/man3/creal.3 b/man3/creal.3 index cb25c6a0e6..ccd33b233c 100644 --- a/man3/creal.3 +++ b/man3/creal.3 @@ -20,7 +20,7 @@ Link with \fI\-lm\fP. .SH DESCRIPTION These functions return the real part of the complex number .IR z . -.LP +.PP One has: .nf diff --git a/man3/ctime.3 b/man3/ctime.3 index bb1b4a6fdd..93e22d1072 100644 --- a/man3/ctime.3 +++ b/man3/ctime.3 @@ -405,11 +405,11 @@ a broken-down time structure and an array of type Execution of any of the functions may overwrite the information returned in either of these objects by any of the other functions." This can occur in the glibc implementation. -.LP +.PP In many implementations, including glibc, a 0 in .I tm_mday is interpreted as meaning the last day of the preceding month. -.LP +.PP The glibc version of \fIstruct tm\fP has additional fields .PP .in +4n diff --git a/man3/des_crypt.3 b/man3/des_crypt.3 index b5348f21de..3ce5aaac52 100644 --- a/man3/des_crypt.3 +++ b/man3/des_crypt.3 @@ -20,15 +20,15 @@ DES encryption .\" Sun version .\" .B #include <des_crypt.h> .B #include <rpc/des_crypt.h> -.LP +.PP .BI "int ecb_crypt(char *" key ", char *" data ", unsigned " datalen , .BI " unsigned " mode ); -.LP +.PP .BI "int cbc_crypt(char *" key ", char *" data ", unsigned " datalen , .BI " unsigned " mode ", char *" ivec ); -.LP +.PP .BI "void des_setparity(char *" key ); -.LP +.PP .BI "int DES_FAILED(int " status ); .fi .SH DESCRIPTION @@ -60,7 +60,7 @@ mode protects against insertions, deletions and substitutions of blocks. Also, regularities in the clear text will not appear in the cipher text. -.LP +.PP Here is how to use these routines. The first argument, .IR key , @@ -118,7 +118,7 @@ An error occurred in the hardware or driver. .BR DESERR_BADPARAM Bad argument to routine. .PD -.LP +.PP Given a result status .IR stat , the macro diff --git a/man3/dirfd.3 b/man3/dirfd.3 index f69e11aa0c..e75fd272ae 100644 --- a/man3/dirfd.3 +++ b/man3/dirfd.3 @@ -52,7 +52,7 @@ The function .BR dirfd () returns the file descriptor associated with the directory stream .IR dirp . -.LP +.PP This file descriptor is the one used internally by the directory stream. As a result, it is useful only for functions which do not depend on or alter the file position, such as diff --git a/man3/div.3 b/man3/div.3 index 057636d45c..a4d884aef3 100644 --- a/man3/div.3 +++ b/man3/div.3 @@ -71,7 +71,7 @@ named \fIdiv_t\fP that contains two integer members (in unspecified order) named \fIquot\fP and \fIrem\fP. The quotient is rounded toward zero. The result satisfies \fIquot\fP*\fIdenominator\fP+\fIrem\fP = \fInumerator\fP. -.LP +.PP The .BR ldiv (), .BR lldiv (), diff --git a/man3/dlopen.3 b/man3/dlopen.3 index 21fad66081..04a9c427d6 100644 --- a/man3/dlopen.3 +++ b/man3/dlopen.3 @@ -470,7 +470,7 @@ this can be done by using the .BR gcc (1) .I \-nostartfiles command-line option. -.LP +.PP Use of .B _init and diff --git a/man3/envz_add.3 b/man3/envz_add.3 index 9d57ef518c..d264eeeb6a 100644 --- a/man3/envz_add.3 +++ b/man3/envz_add.3 @@ -35,7 +35,7 @@ envz_remove, envz_strip \- environment string support .fi .SH DESCRIPTION These functions are glibc-specific. -.LP +.PP An argz vector is a pointer to a character buffer together with a length, see .BR argz_add (3). @@ -45,9 +45,9 @@ Everything after the first \(aq=\(aq is considered to be the value. If there is no \(aq=\(aq, the value is taken to be NULL. (While the value in case of a trailing \(aq=\(aq is the empty string "".) -.LP +.PP These functions are for handling envz vectors. -.LP +.PP .BR envz_add () adds the string .RI \&" name = value \&" @@ -66,14 +66,14 @@ and If an entry with the same .I name existed, it is removed. -.LP +.PP .BR envz_entry () looks for .I name in the envz vector .RI ( envz ,\ envz_len ) and returns the entry if found, or NULL if not. -.LP +.PP .BR envz_get () looks for .I name @@ -84,7 +84,7 @@ and returns the value if found, or NULL if not. an entry for .I name without \(aq=\(aq sign.) -.LP +.PP .BR envz_merge () adds each entry in .I envz2 @@ -99,14 +99,14 @@ is true, then values in will supersede those with the same name in .IR *envz , otherwise not. -.LP +.PP .BR envz_remove () removes the entry for .I name from .RI ( *envz ,\ *envz_len ) if there was one. -.LP +.PP .BR envz_strip () removes all entries with value NULL. .SH RETURN VALUE diff --git a/man3/exit.3 b/man3/exit.3 index 921be46fbc..c738939467 100644 --- a/man3/exit.3 +++ b/man3/exit.3 @@ -42,7 +42,7 @@ function causes normal process termination and the value of \fIstatus & 0377\fP is returned to the parent (see .BR wait (2)). -.LP +.PP All functions registered with .BR atexit (3) and @@ -69,14 +69,14 @@ If a function has been registered multiple times using or .BR on_exit (3), then it is called as many times as it was registered. -.LP +.PP All open .BR stdio (3) streams are flushed and closed. Files created by .BR tmpfile (3) are removed. -.LP +.PP The C standard specifies two constants, \fBEXIT_SUCCESS\fP and \fBEXIT_FAILURE\fP, that may be passed to @@ -107,7 +107,7 @@ so it is not thread-safe. .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD. .SH NOTES -.LP +.PP It is undefined what happens if one of the functions registered using .BR atexit (3) @@ -123,7 +123,7 @@ removes registrations created using .BR atexit (3) and .BR on_exit (3). -.LP +.PP The use of .B EXIT_SUCCESS and @@ -132,10 +132,10 @@ is slightly more portable (to non-UNIX environments) than the use of 0 and some nonzero value like 1 or \-1. In particular, VMS uses a different convention. -.LP +.PP BSD has attempted to standardize exit codes; see the file .IR <sysexits.h> . -.LP +.PP After .BR exit (), the exit status must be transmitted to the @@ -162,7 +162,7 @@ This allows the parent to subsequently use .BR waitpid (2) (or similar) to learn the termination status of the child; at that point the zombie process slot is released. -.LP +.PP If the implementation supports the .B SIGCHLD signal, this signal @@ -172,7 +172,7 @@ If the parent has set it is undefined whether a .B SIGCHLD signal is sent. -.LP +.PP If the process is a session leader and its controlling terminal is the controlling terminal of the session, then each process in the foreground process group of this controlling terminal @@ -181,7 +181,7 @@ is sent a signal, and the terminal is disassociated from this session, allowing it to be acquired by a new controlling process. -.LP +.PP If the exit of the process causes a process group to become orphaned, and if any member of the newly orphaned process group is stopped, then a diff --git a/man3/fenv.3 b/man3/fenv.3 index 7a93e83920..dd11754106 100644 --- a/man3/fenv.3 +++ b/man3/fenv.3 @@ -66,20 +66,20 @@ The .I divide-by-zero exception occurs when an operation on finite numbers produces infinity as exact answer. -.LP +.PP The .I overflow exception occurs when a result has to be represented as a floating-point number, but has (much) larger absolute value than the largest (finite) floating-point number that is representable. -.LP +.PP The .I underflow exception occurs when a result has to be represented as a floating-point number, but has smaller absolute value than the smallest positive normalized floating-point number (and would lose much accuracy when represented as a denormalized number). -.LP +.PP The .I inexact exception occurs when the rounded result of an operation @@ -89,7 +89,7 @@ It may occur whenever or .I underflow occurs. -.LP +.PP The .I invalid exception occurs when there is no well-defined result @@ -100,7 +100,7 @@ Exceptions are represented in two ways: as a single bit implementation-defined way with bit positions in an integer, and also as an opaque structure that may contain more information about the exception (perhaps the code address where it occurred). -.LP +.PP Each of the macros .BR FE_DIVBYZERO , .BR FE_INEXACT , @@ -121,7 +121,7 @@ The .BR feclearexcept () function clears the supported exceptions represented by the bits in its argument. -.LP +.PP The .BR fegetexceptflag () function stores a representation of the state of the exception flags @@ -129,12 +129,12 @@ represented by the argument .I excepts in the opaque object .IR *flagp . -.LP +.PP The .BR feraiseexcept () function raises the supported exceptions represented by the bits in .IR excepts . -.LP +.PP The .BR fesetexceptflag () function sets the complete status for the exceptions represented by @@ -145,7 +145,7 @@ This value must have been obtained by an earlier call of .BR fegetexceptflag () with a last argument that contained all bits in .IR excepts . -.LP +.PP The .BR fetestexcept () function returns a word in which the bits are set that were @@ -169,12 +169,12 @@ and .BR FE_TOWARDZERO is defined when the implementation supports getting and setting the corresponding rounding direction. -.LP +.PP The .BR fegetround () function returns the macro corresponding to the current rounding mode. -.LP +.PP The .BR fesetround () function sets the rounding mode as specified by its argument @@ -217,19 +217,19 @@ The default environment is denoted by This is the environment setup at program start and it is defined by ISO C to have round to nearest, all exceptions cleared and a nonstop (continue on exceptions) mode. -.LP +.PP The .BR fegetenv () function saves the current floating-point environment in the object .IR *envp . -.LP +.PP The .BR feholdexcept () function does the same, then clears all exception flags, and sets a nonstop (continue on exceptions) mode, if available. It returns zero when successful. -.LP +.PP The .BR fesetenv () function restores the floating-point environment from @@ -242,7 +242,7 @@ or or equal to .BR FE_DFL_ENV . This call does not raise exceptions. -.LP +.PP The .BR feupdateenv () function installs the floating-point environment represented by diff --git a/man3/flockfile.3 b/man3/flockfile.3 index ca1a00d9ba..1a40c02cb2 100644 --- a/man3/flockfile.3 +++ b/man3/flockfile.3 @@ -61,13 +61,13 @@ For each library call, these functions wait until the object is no longer locked by a different thread, then lock it, do the requested I/O, and unlock the object again. -.LP +.PP (Note: this locking has nothing to do with the file locking done by functions like .BR flock (2) and .BR lockf (3).) -.LP +.PP All this is invisible to the C-programmer, but there may be two reasons to wish for more detailed control. On the one hand, maybe @@ -75,7 +75,7 @@ a series of I/O actions by one thread belongs together, and should not be interrupted by the I/O of some other thread. On the other hand, maybe the locking overhead should be avoided for greater efficiency. -.LP +.PP To this end, a thread can explicitly lock the .I FILE object, @@ -92,7 +92,7 @@ instead of .BR getc (3) and .BR putc (3). -.LP +.PP The .BR flockfile () function waits for @@ -103,11 +103,11 @@ current thread owner of .IR *filehandle , and increments the lockcount. -.LP +.PP The .BR funlockfile () function decrements the lock count. -.LP +.PP The .BR ftrylockfile () function is a nonblocking version diff --git a/man3/fmtmsg.3 b/man3/fmtmsg.3 index a7a7b1aea5..5099edc563 100644 --- a/man3/fmtmsg.3 +++ b/man3/fmtmsg.3 @@ -33,23 +33,23 @@ For messages written to the format depends on the .B MSGVERB environment variable. -.LP +.PP The .I label argument identifies the source of the message. The string must consist of two colon separated parts where the first part has not more than 10 and the second part not more than 14 characters. -.LP +.PP The .I text argument describes the condition of the error. -.LP +.PP The .I action argument describes possible steps to recover from the error. If it is printed, it is prefixed by "TO FIX: ". -.LP +.PP The .I tag argument is a reference to the online documentation where more @@ -204,7 +204,7 @@ then will also accept the indicated values for the level (in addition to the standard levels 0-4), and use the indicated printstring when such a level occurs. -.LP +.PP The severity-keyword part is not used by .BR fmtmsg () but it has to be present. diff --git a/man3/fpclassify.3 b/man3/fpclassify.3 index 76fd59a06f..85a42c38a4 100644 --- a/man3/fpclassify.3 +++ b/man3/fpclassify.3 @@ -86,7 +86,7 @@ is too small to be represented in normalized format. .B FP_NORMAL if nothing of the above is correct then it must be a normal floating-point number. -.LP +.PP The other macros provide a short answer to some standard questions. .TP 14 .BI isfinite( x ) diff --git a/man3/fpurge.3 b/man3/fpurge.3 index 627ffa364d..2d35130466 100644 --- a/man3/fpurge.3 +++ b/man3/fpurge.3 @@ -51,7 +51,7 @@ this includes any text pushed back via .BR ungetc (3). See also .BR fflush (3). -.LP +.PP The function .BR __fpurge () does precisely the same, but without returning a value. diff --git a/man3/fseeko.3 b/man3/fseeko.3 index 6793633ede..37b696b008 100644 --- a/man3/fseeko.3 +++ b/man3/fseeko.3 @@ -71,7 +71,7 @@ is of type .I off_t instead of .IR long . -.LP +.PP On some architectures, both .IR off_t and diff --git a/man3/ftime.3 b/man3/ftime.3 index 7f153b7296..9977b308c3 100644 --- a/man3/ftime.3 +++ b/man3/ftime.3 @@ -51,7 +51,7 @@ struct timeb { }; .fi .in -.LP +.PP Here \fItime\fP is the number of seconds since the Epoch, and \fImillitm\fP is the number of milliseconds since \fItime\fP seconds since the Epoch. @@ -61,7 +61,7 @@ east of Greenwich). The \fIdstflag\fP field is a flag that, if nonzero, indicates that Daylight Saving time applies locally during the appropriate part of the year. -.LP +.PP POSIX.1-2001 says that the contents of the \fItimezone\fP and \fIdstflag\fP fields are unspecified; avoid relying on them. .SH RETURN VALUE @@ -95,7 +95,7 @@ gives microseconds; .BR clock_gettime (2) gives nanoseconds but is not as widely available. .SH BUGS -.LP +.PP Early glibc2 is buggy and returns 0 in the .I millitm field; diff --git a/man3/ftok.3 b/man3/ftok.3 index 859a05f132..cd185d481c 100644 --- a/man3/ftok.3 +++ b/man3/ftok.3 @@ -51,7 +51,7 @@ type System V IPC key, suitable for use with .BR semget (2), or .BR shmget (2). -.LP +.PP The resulting value is the same for all pathnames that name the same file, when the same value of .I proj_id @@ -100,7 +100,7 @@ Typical usage has an ASCII character that is why the behavior is said to be undefined when .I proj_id is zero. -.LP +.PP Of course, no guarantee can be given that the resulting .I key_t is unique. diff --git a/man3/ftw.3 b/man3/ftw.3 index e9a358a7c9..0d87d0e3b0 100644 --- a/man3/ftw.3 +++ b/man3/ftw.3 @@ -398,7 +398,7 @@ The function and the use of \fBFTW_SL\fP with .BR ftw () were introduced in SUSv1. -.LP +.PP In some implementations (e.g., glibc), .BR ftw () will never use \fBFTW_SL\fP, on other systems \fBFTW_SL\fP occurs only diff --git a/man3/getcontext.3 b/man3/getcontext.3 index 6af4da8664..0a9981a84c 100644 --- a/man3/getcontext.3 +++ b/man3/getcontext.3 @@ -46,7 +46,7 @@ and .BR swapcontext (3) that allow user-level context switching between multiple threads of control within a process. -.LP +.PP The .I mcontext_t type is machine-dependent and opaque. @@ -91,14 +91,14 @@ and is the machine-specific representation of the saved context, that includes the calling thread's machine registers. -.LP +.PP The function .BR getcontext () initializes the structure pointed at by .I ucp to the currently active context. -.LP +.PP The function .BR setcontext () restores the user context @@ -111,11 +111,11 @@ or .BR makecontext (3), or passed as third argument to a signal handler. -.LP +.PP If the context was obtained by a call of .BR getcontext (), program execution continues as if this call just returned. -.LP +.PP If the context was obtained by a call of .BR makecontext (3), program execution continues by a call to the function @@ -132,7 +132,7 @@ specified as the first argument of that call to .BR makecontext (3). When this member is NULL, the thread exits. -.LP +.PP If the context was obtained by a call to a signal handler, then old standard text says that "program execution continues with the program instruction following the instruction interrupted @@ -186,7 +186,7 @@ is from the first call, or via a call. The user has to invent her own bookkeeping device, and a register variable won't do since registers are restored. -.LP +.PP When a signal occurs, the current user context is saved and a new context is created by the kernel for the signal handler. Do not leave the handler using diff --git a/man3/getcwd.3 b/man3/getcwd.3 index 879e2dd006..d9095129ac 100644 --- a/man3/getcwd.3 +++ b/man3/getcwd.3 @@ -270,7 +270,7 @@ generic implementation is called. Only in that case can these calls fail under Linux with .BR EACCES . -.LP +.PP These functions are often used to save the location of the current working directory for the purpose of returning to it later. Opening the current diff --git a/man3/getdate.3 b/man3/getdate.3 index 585b9841ce..370b9150f2 100644 --- a/man3/getdate.3 +++ b/man3/getdate.3 @@ -102,7 +102,7 @@ Timezone name. .\" Looking at the glibc 2.21 source code, where the implementation uses .\" strptime(), suggests that it might be supported. This is not implemented in glibc. -.LP +.PP When .B %Z is given, the structure containing the broken-down time @@ -111,18 +111,18 @@ time in the given timezone. Otherwise, the structure is initialized to the broken-down time corresponding to the current local time (as by a call to .BR localtime (3)). -.LP +.PP When only the day of the week is given, the day is taken to be the first such day on or after today. -.LP +.PP When only the month is given (and no year), the month is taken to be the first such month equal to or after the current month. If no day is given, it is the first day of the month. -.LP +.PP When no hour, minute and second are given, the current hour, minute and second are taken. -.LP +.PP 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 diff --git a/man3/getfsent.3 b/man3/getfsent.3 index 40a9993483..55eb2d85d5 100644 --- a/man3/getfsent.3 +++ b/man3/getfsent.3 @@ -45,7 +45,7 @@ These functions read from the file The .IR "struct fstab" is defined by: -.LP +.PP .in +4n .nf struct fstab { @@ -69,16 +69,16 @@ one of the five strings "rw", "rq", "ro", "sw", "xx" The function .BR setfsent () opens the file when required and positions it at the first line. -.LP +.PP The function .BR getfsent () parses the next line from the file. (After opening it when required.) -.LP +.PP The function .BR endfsent () closes the file when required. -.LP +.PP The function .BR getfsspec () searches the file from the start and returns the first entry found @@ -87,7 +87,7 @@ for which the field matches the .I special_file argument. -.LP +.PP The function .BR getfsfile () searches the file from the start and returns the first entry found @@ -147,7 +147,7 @@ and calls these functions obsolete, superseded by .BR getmntent (3). .SH NOTES These functions are not thread-safe. -.LP +.PP Since Linux allows mounting a block special device in several places, and since several devices can have the same mount point, where the last device with a given mount point is the interesting one, diff --git a/man3/getgrent.3 b/man3/getgrent.3 index 5bb1d79b80..2b17b0690c 100644 --- a/man3/getgrent.3 +++ b/man3/getgrent.3 @@ -119,7 +119,7 @@ function returns a pointer to a .I group structure, or NULL if there are no more entries or an error occurs. -.LP +.PP Upon error, .I errno may be set. diff --git a/man3/getgrnam.3 b/man3/getgrnam.3 index 52035a13fb..156c137771 100644 --- a/man3/getgrnam.3 +++ b/man3/getgrnam.3 @@ -149,7 +149,7 @@ is set appropriately. If one wants to check .I errno after the call, it should be set to zero before the call. -.LP +.PP The return value may point to a static area, and may be overwritten by subsequent calls to .BR getgrent (3), @@ -158,7 +158,7 @@ or .BR getgrnam (). (Do not pass the returned pointer to .BR free (3).) -.LP +.PP On success, .BR getgrnam_r () and diff --git a/man3/gethostbyname.3 b/man3/gethostbyname.3 index 58be1fe882..16a479a606 100644 --- a/man3/gethostbyname.3 +++ b/man3/gethostbyname.3 @@ -444,7 +444,7 @@ later calls. Copying the .I struct hostent does not suffice, since it contains pointers; a deep copy is required. -.LP +.PP In the original BSD implementation the .I len argument @@ -468,7 +468,7 @@ POSIX.1-2001 makes it which is OK.) See also .BR accept (2). -.LP +.PP The BSD prototype for .BR gethostbyaddr () uses @@ -497,7 +497,7 @@ Glibc2 also has a that works like .BR gethostbyname (), but permits to specify the address family to which the address must belong. -.LP +.PP Glibc2 also has reentrant versions .BR gethostent_r (), .BR gethostbyaddr_r (), diff --git a/man3/getipnodebyname.3 b/man3/getipnodebyname.3 index a8f3e2ac51..f6f384497b 100644 --- a/man3/getipnodebyname.3 +++ b/man3/getipnodebyname.3 @@ -48,7 +48,7 @@ Use and .BR getnameinfo (3) instead. -.LP +.PP The .BR getipnodebyname () and diff --git a/man3/getlogin.3 b/man3/getlogin.3 index b79fe2c3ae..1c707a3dec 100644 --- a/man3/getlogin.3 +++ b/man3/getlogin.3 @@ -124,7 +124,7 @@ The calling process has no controlling terminal. The length of the username, including the terminating null byte (\(aq\\0\(aq), is larger than .IR bufsize . -.LP +.PP Linux/glibc also has .TP .B ENOENT @@ -203,7 +203,7 @@ function was included in the 1988 version of POSIX, but removed from the 1990 version. It was present in SUSv2, but removed in POSIX.1-2001. -.LP +.PP OpenBSD has .BR getlogin () and @@ -222,7 +222,7 @@ of our program need not be the user who started it. Avoid .BR getlogin () for security-related purposes. -.LP +.PP Note that glibc does not follow the POSIX specification and uses .I stdin instead of @@ -232,7 +232,7 @@ A bug. all return the login name also when .I stdin is redirected.) -.LP +.PP Nobody knows precisely what .BR cuserid () does; avoid it in portable programs. diff --git a/man3/getpwnam.3 b/man3/getpwnam.3 index de8a702452..9066f46887 100644 --- a/man3/getpwnam.3 +++ b/man3/getpwnam.3 @@ -153,7 +153,7 @@ is set appropriately. If one wants to check .I errno after the call, it should be set to zero before the call. -.LP +.PP The return value may point to a static area, and may be overwritten by subsequent calls to .BR getpwent (3), @@ -162,7 +162,7 @@ or .BR getpwuid (). (Do not pass the returned pointer to .BR free (3).) -.LP +.PP On success, .BR getpwnam_r () and diff --git a/man3/getrpcent.3 b/man3/getrpcent.3 index a126a4e2df..cbd76aaa4a 100644 --- a/man3/getrpcent.3 +++ b/man3/getrpcent.3 @@ -24,7 +24,7 @@ RPC entry .BI "void endrpcent(void);" .fi .SH DESCRIPTION -.LP +.PP The .BR getrpcent (), .BR getrpcbyname (), @@ -43,7 +43,7 @@ struct rpcent { }; .fi .in -.LP +.PP The members of this structure are: .RS 4 .TP 12 @@ -56,12 +56,12 @@ A NULL-terminated list of alternate names for the RPC program. .I r_number The RPC program number for this service. .RE -.LP +.PP The .BR getrpcent () function reads the next entry from the database. A connection is opened to the database if necessary. -.LP +.PP The .BR setrpcent () function opens a connection to the database, @@ -73,11 +73,11 @@ then the connection to the database will not be closed between calls to one of the .BR getrpc* () functions. -.LP +.PP The .BR endrpcent () function closes the connection to the database. -.LP +.PP The .BR getrpcbyname () and diff --git a/man3/getspnam.3 b/man3/getspnam.3 index 4cfac0edde..a08d019d8b 100644 --- a/man3/getspnam.3 +++ b/man3/getspnam.3 @@ -76,7 +76,7 @@ the shadow password database .IR /etc/shadow , NIS, and LDAP), readable only by root. -.LP +.PP The functions described below resemble those for the traditional password database (e.g., see @@ -93,14 +93,14 @@ and .\" (pluggable authentication modules), and the file .\" .I /etc/nsswitch.conf .\" now describes the sources to be used. -.LP +.PP The .BR getspnam () function returns a pointer to a structure containing the broken-out fields of the record in the shadow password database that matches the username .IR name . -.LP +.PP The .BR getspent () function returns a pointer to the next entry in the shadow password @@ -112,21 +112,21 @@ When done reading, the program may call so that resources can be deallocated. .\" some systems require a call of setspent() before the first getspent() .\" glibc does not -.LP +.PP The .BR fgetspent () function is similar to .BR getspent () but uses the supplied stream instead of the one implicitly opened by .BR setspent (). -.LP +.PP The .BR sgetspent () function parses the supplied string .I s into a struct .IR spwd . -.LP +.PP The .BR putspent () function writes the contents of the supplied struct @@ -136,7 +136,7 @@ as a text line in the shadow password file format to .IR stream . String entries with value NULL and numerical entries with value \-1 are written as an empty string. -.LP +.PP The .BR lckpwdf () function is intended to protect against multiple simultaneous accesses @@ -151,7 +151,7 @@ password file. Only programs that use .BR lckpwdf () will notice the lock. -.LP +.PP These were the functions that formed the original shadow API. They are widely available. .\" Also in libc5 @@ -173,14 +173,14 @@ of size A pointer to the result (in case of success) or NULL (in case no entry was found or an error occurred) is stored in .IR *spbufp . -.LP +.PP The functions .BR getspent_r (), .BR fgetspent_r (), and .BR sgetspent_r () are similarly analogous to their nonreentrant counterparts. -.LP +.PP Some non-glibc systems also have functions with these names, often with different prototypes. .\" SUN doesn't have sgetspent_r() @@ -215,10 +215,10 @@ The functions which have \fIint\fP as the return value return 0 for success and \-1 for failure, with .I errno set to indicate the cause of the error. -.LP +.PP For the nonreentrant functions, the return value may point to static area, and may be overwritten by subsequent calls to these functions. -.LP +.PP The reentrant functions return zero on success. In case of error, an error number is returned. .SH ERRORS @@ -235,7 +235,7 @@ local shadow password database file .TP .I /etc/.pwd.lock lock file -.LP +.PP The include file .I <paths.h> defines the constant diff --git a/man3/getutent.3 b/man3/getutent.3 index 4b4dc73074..caeb686590 100644 --- a/man3/getutent.3 +++ b/man3/getutent.3 @@ -212,7 +212,7 @@ are used in parallel in different threads of a program, then data races could occur. .SH CONFORMING TO XPG2, SVr4. -.LP +.PP In XPG2 and SVID 2 the function .BR pututline () is documented to return void, and that is what it does on many systems @@ -221,7 +221,7 @@ HP-UX introduces a new function .BR _pututline () with the prototype given above for .BR pututline (). -.LP +.PP All these functions are obsolete now on non-Linux systems. POSIX.1-2001 and POSIX.1-2008, following SUSv1, does not have any of these functions, but instead uses @@ -255,7 +255,7 @@ and parallel files are maintained, often .I /var/*/utmpx and .IR /var/*/wtmpx . -.LP +.PP Linux glibc on the other hand does not use a parallel \fIutmpx\fP file since its \fIutmp\fP structure is already large enough. The "x" functions listed above are just aliases for diff --git a/man3/gsignal.3 b/man3/gsignal.3 index 30a5c657db..cd666c8e3a 100644 --- a/man3/gsignal.3 +++ b/man3/gsignal.3 @@ -57,7 +57,7 @@ aliases for and .BR signal (2), respectively. -.LP +.PP Elsewhere, on System V-like systems, these functions implement software signaling, entirely independent of the classical .BR signal (2) diff --git a/man3/hsearch.3 b/man3/hsearch.3 index c267dfd9c3..7d06d18cdb 100644 --- a/man3/hsearch.3 +++ b/man3/hsearch.3 @@ -194,7 +194,7 @@ In the event of an error, these two functions set .I errno to indicate the cause of the error. .SH ERRORS -.LP +.PP .BR hcreate_r () and .BR hdestroy_r () diff --git a/man3/lockf.3 b/man3/lockf.3 index 9d3175f6fb..d2dd520915 100644 --- a/man3/lockf.3 +++ b/man3/lockf.3 @@ -68,7 +68,7 @@ is the current file position, and if is zero, the section extends from the current file position to infinity, encompassing the present and future end-of-file positions. In all cases, the section may extend past current end-of-file. -.LP +.PP On Linux, .BR lockf () is just an interface on top of @@ -83,7 +83,7 @@ and locks unspecified. A portable application should probably avoid mixing calls to these interfaces. -.LP +.PP Valid operations are given below: .TP .B F_LOCK diff --git a/man3/logb.3 b/man3/logb.3 index b183fd25fd..577dc31fc8 100644 --- a/man3/logb.3 +++ b/man3/logb.3 @@ -80,7 +80,7 @@ is 2, is equal to .BI floor(log2( x ))\fR, except that it is probably faster. -.LP +.PP If .I x is subnormal, diff --git a/man3/login.3 b/man3/login.3 index 373469d79a..2d9b82d8a4 100644 --- a/man3/login.3 +++ b/man3/login.3 @@ -38,14 +38,14 @@ The utmp file records who is currently using the system. The wtmp file records all logins and logouts. See .BR utmp (5). -.LP +.PP The function .BR login () takes the supplied .IR "struct utmp" , .IR ut , and writes it to both the utmp and the wtmp file. -.LP +.PP The function .BR logout () clears the entry in the utmp file again. @@ -75,7 +75,7 @@ On the other hand, if no terminal name was found, this field is filled with "???" and the struct is not written to the utmp file. After this, the struct is written to the wtmp file. -.LP +.PP The .BR logout () function searches the utmp file for an entry matching the diff --git a/man3/lseek64.3 b/man3/lseek64.3 index c15afd4690..0b119e8b06 100644 --- a/man3/lseek64.3 +++ b/man3/lseek64.3 @@ -50,7 +50,7 @@ has the value or .BR SEEK_END , respectively. -.LP +.PP For more details, return value, and errors, see .BR lseek (2). .PP diff --git a/man3/makecontext.3 b/man3/makecontext.3 index dde30ae7db..e2326505c0 100644 --- a/man3/makecontext.3 +++ b/man3/makecontext.3 @@ -46,10 +46,10 @@ and .BR swapcontext () that allow user-level context switching between multiple threads of control within a process. -.LP +.PP For the type and the first two functions, see .BR getcontext (3). -.LP +.PP The .BR makecontext () function modifies the context pointed to @@ -75,7 +75,7 @@ the caller must specify the number of these arguments in .IR argc . When this function returns, the successor context is activated. If the successor context pointer is NULL, the thread exits. -.LP +.PP The .BR swapcontext () function saves the current context in diff --git a/man3/malloc.3 b/man3/malloc.3 index af706909c1..502c4c8ba4 100644 --- a/man3/malloc.3 +++ b/man3/malloc.3 @@ -330,7 +330,7 @@ use a private malloc implementation that does not set then certain library routines may fail without having a reason in .IR errno . -.LP +.PP Crashes in .BR malloc (), .BR calloc (), diff --git a/man3/malloc_hook.3 b/man3/malloc_hook.3 index 9c871b9eee..e95bcb4407 100644 --- a/man3/malloc_hook.3 +++ b/man3/malloc_hook.3 @@ -40,7 +40,7 @@ by specifying appropriate hook functions. You can use these hooks to help you debug programs that use dynamic memory allocation, for example. -.LP +.PP The variable .B __malloc_initialize_hook points at a function that is called once when the malloc implementation @@ -55,7 +55,7 @@ the application with a definition like the following: Now the function .IR my_init_hook () can do the initialization of all hooks. -.LP +.PP The four functions pointed to by .BR __malloc_hook , .BR __realloc_hook , @@ -71,7 +71,7 @@ respectively, except that they have a final argument that gives the address of the caller of .BR malloc (3), etc. -.LP +.PP The variable .B __after_morecore_hook points at a function that is called each time after diff --git a/man3/nan.3 b/man3/nan.3 index f60a89ead7..265d5224c4 100644 --- a/man3/nan.3 +++ b/man3/nan.3 @@ -41,7 +41,7 @@ These functions return a representation (determined by of a quiet NaN. If the implementation does not support quiet NaNs, these functions return zero. -.LP +.PP The call .I nan("char-sequence") is equivalent to: diff --git a/man3/nl_langinfo.3 b/man3/nl_langinfo.3 index b28dbbd3a1..461de5a769 100644 --- a/man3/nl_langinfo.3 +++ b/man3/nl_langinfo.3 @@ -193,7 +193,7 @@ or is not a valid locale object handle. The following program sets the character type and the numeric locale according to the environment and queries the terminal character set and the radix character. -.LP +.PP .nf #include <langinfo.h> #include <locale.h> diff --git a/man3/openpty.3 b/man3/openpty.3 index 90742ebca6..c779d17a1c 100644 --- a/man3/openpty.3 +++ b/man3/openpty.3 @@ -134,14 +134,14 @@ will fail if: .TP .B ENOENT There are no available terminals. -.LP +.PP .BR login_tty () will fail if .BR ioctl (2) fails to set .I fd to the controlling terminal of the calling process. -.LP +.PP .BR forkpty () will fail if either .BR openpty () diff --git a/man3/posix_spawn.3 b/man3/posix_spawn.3 index c6e0c61f16..24ea7e6e36 100644 --- a/man3/posix_spawn.3 +++ b/man3/posix_spawn.3 @@ -203,7 +203,7 @@ does \fInot\fP contain .BR POSIX_SPAWN_SETPGROUP , or .BR POSIX_SPAWN_RESETIDS . -.LP +.PP In other words, .BR vfork (2) is used if the caller requests it, @@ -245,7 +245,7 @@ functions. File descriptors with the .B FD_CLOEXEC flag set are closed. -.LP +.PP All process attributes in the child, other than those affected by attributes specified in the object pointed to by @@ -267,7 +267,7 @@ attribute (set using controls the general actions that occur, and other attributes in the object specify values to be used during those actions. -.LP +.PP The effects of the flags that may be specified in .IR spawn-flags are as follows: @@ -339,7 +339,7 @@ attribute of the object pointed to by .IR attrp (but see BUGS). -.LP +.PP If the .B POSIX_SPAWN_SETSCHEDPARAM and @@ -375,7 +375,7 @@ the child's process group ID is made the same as its process ID. If the .B POSIX_SPAWN_SETPGROUP flag is not set, the child inherits the parent's process group ID. -.LP +.PP If .I attrp is NULL, then the default behaviors described above for each flag apply. @@ -403,7 +403,7 @@ except those for which the .B FD_CLOEXEC flag has been set. File locks remain in place. -.LP +.PP If .I file_actions is not NULL, then it contains an ordered set of requests to @@ -442,7 +442,7 @@ the child process exits with exit value 127. Once the child has successfully forked and performed all requested pre-exec steps, the child runs the requested executable. -.LP +.PP The child process takes its environment from the .I envp argument, which is interpreted as if it had been passed to @@ -488,7 +488,7 @@ which will be one of the errors described for .BR fork (2) or .BR vfork (2). -.LP +.PP In addition, these functions fail if: .TP .B ENOSYS @@ -500,7 +500,7 @@ and .BR posix_spawnp () functions are available since glibc 2.2. .SH CONFORMING TO -.LP +.PP POSIX.1-2001, POSIX.1-2008. .\" FIXME . This piece belongs in spawnattr_setflags(3) .\" The diff --git a/man3/putenv.3 b/man3/putenv.3 index 3e7ea0b678..7a26c476eb 100644 --- a/man3/putenv.3 +++ b/man3/putenv.3 @@ -110,7 +110,7 @@ one in glibc 2.0 is not, but the glibc 2.1 version is. .\" then it will be freed. .\" In no case will the old storage associated .\" to the environment variable itself be freed. -.LP +.PP Since version 2.1.2, the glibc implementation conforms to SUSv2: the pointer \fIstring\fP given to .BR putenv () @@ -125,9 +125,9 @@ is still part of the environment.) However, glibc versions 2.0 to 2.1.1 differ: a copy of the string is used. On the one hand this causes a memory leak, and on the other hand it violates SUSv2. -.LP +.PP The 4.4BSD version, like glibc 2.0, uses a copy. -.LP +.PP SUSv2 removes the \fIconst\fP from the prototype, and so does glibc 2.1.3. .SH SEE ALSO .BR clearenv (3), diff --git a/man3/realpath.3 b/man3/realpath.3 index e4985009d4..57efb816bc 100644 --- a/man3/realpath.3 +++ b/man3/realpath.3 @@ -168,7 +168,7 @@ as found in \fI<limits.h>\fP or provided by the .BR pathconf (3) function. A typical source fragment would be -.LP +.PP .in +4n .nf #ifdef PATH_MAX @@ -180,9 +180,9 @@ A typical source fragment would be #endif .fi .in -.LP +.PP (But see the BUGS section.) -.LP +.PP .\" 2012-05-05, According to Casper Dik, the statement about .\" Solaris was not true at least as far back as 1997, and .\" may never have been true. diff --git a/man3/remainder.3 b/man3/remainder.3 index 7527fe5bc9..84efc059cc 100644 --- a/man3/remainder.3 +++ b/man3/remainder.3 @@ -107,7 +107,7 @@ is chosen to be even. .PP These functions are unaffected by the current rounding mode (see .BR fenv (3)). -.LP +.PP The .BR drem () function does precisely the same thing. diff --git a/man3/rint.3 b/man3/rint.3 index c20ef94c98..923584926d 100644 --- a/man3/rint.3 +++ b/man3/rint.3 @@ -92,7 +92,7 @@ exception. When the current rounding direction is to nearest, these functions round halfway cases to the even integer in accordance with IEEE-754. -.LP +.PP The .BR rint (), .BR rintf (), diff --git a/man3/rpc.3 b/man3/rpc.3 index b45283e87d..c423e69e73 100644 --- a/man3/rpc.3 +++ b/man3/rpc.3 @@ -23,7 +23,7 @@ Finally, the procedure call returns to the client. .\" Routines that are used for Secure RPC (DES authentication) are described in .\" .BR rpc_secure (3). .\" Secure RPC can be used only if DES encryption is available. -.LP +.PP To take use of these routines, include the header file .IR "<rpc/rpc.h>" . @@ -39,7 +39,7 @@ The prototypes below make use of the following types: .BI " struct sockaddr_in *" raddr ); .fi .in -.LP +.PP See the header files for the declarations of the .IR AUTH , .IR CLIENT , @@ -47,7 +47,7 @@ See the header files for the declarations of the and .IR XDR types. -.LP +.PP .nf .BI "void auth_destroy(AUTH *" auth ); .fi @@ -59,7 +59,7 @@ The use of .I auth is undefined after calling .BR auth_destroy (). -.LP +.PP .nf .BI "AUTH *authnone_create(void);" .fi @@ -68,7 +68,7 @@ Create and return an RPC authentication handle that passes nonusable authentication information with each remote procedure call. This is the default authentication used by RPC. -.LP +.PP .nf .BI "AUTH *authunix_create(char *" host ", int " uid ", int " gid , .BI " int " len ", int *" aup_gids ); @@ -88,7 +88,7 @@ and .I aup_gids refer to a counted array of groups to which the user belongs. It is easy to impersonate a user. -.LP +.PP .nf .BI "AUTH *authunix_create_default(void);" .fi @@ -96,7 +96,7 @@ It is easy to impersonate a user. Calls .BR authunix_create () with the appropriate parameters. -.LP +.PP .nf .BI "int callrpc(char *" host ", unsigned long " prognum , .BI " unsigned long " versnum ", unsigned long " procnum , @@ -132,7 +132,7 @@ uses UDP/IP as a transport; see .BR clntudp_create () for restrictions. You do not have control of timeouts or authentication using this routine. -.LP +.PP .nf .BI "enum clnt_stat clnt_broadcast(unsigned long " prognum , .BI " unsigned long " versnum ", unsigned long " procnum , @@ -173,7 +173,7 @@ waits for more replies; otherwise it returns with appropriate status. Warning: broadcast sockets are limited in size to the maximum transfer unit of the data link. For ethernet, this value is 1500 bytes. -.LP +.PP .nf .BI "enum clnt_stat clnt_call(CLIENT *" clnt ", unsigned long " procnum , .BI " xdrproc_t " inproc ", char *" in , @@ -198,7 +198,7 @@ is used to encode the procedure's parameters, and is used to decode the procedure's results; .I tout is the time allowed for results to come back. -.LP +.PP .nf .BI "clnt_destroy(CLIENT *" clnt ); .fi @@ -214,7 +214,7 @@ is undefined after calling .BR clnt_destroy (). If the RPC library opened the associated socket, it will close it also. Otherwise, the socket remains open. -.LP +.PP .nf .BI "CLIENT *clnt_create(char *" host ", unsigned long " prog , .BI " unsigned long " vers ", char *" proto ); @@ -234,7 +234,7 @@ Warning: using UDP has its shortcomings. Since UDP-based RPC messages can hold only up to 8 Kbytes of encoded data, this transport cannot be used for procedures that take large arguments or return huge results. -.LP +.PP .nf .BI "bool_t clnt_control(CLIENT *" cl ", int " req ", char *" info ); .fi @@ -280,7 +280,7 @@ The following operations are valid for UDP only: The retry timeout is the time that "UDP RPC" waits for the server to reply before retransmitting the request. -.LP +.PP .nf .BI "clnt_freeres(CLIENT * " clnt ", xdrproc_t " outproc ", char *" out ); .fi @@ -294,7 +294,7 @@ is the address of the results, and is the XDR routine describing the results. This routine returns one if the results were successfully freed, and zero otherwise. -.LP +.PP .nf .BI "void clnt_geterr(CLIENT *" clnt ", struct rpc_err *" errp ); .fi @@ -302,7 +302,7 @@ and zero otherwise. A macro that copies the error structure out of the client handle to the structure at address .IR errp . -.LP +.PP .nf .BI "void clnt_pcreateerror(char *" s ); .fi @@ -319,7 +319,7 @@ Used when a or .BR clntudp_create () call fails. -.LP +.PP .nf .BI "void clnt_perrno(enum clnt_stat " stat ); .fi @@ -329,7 +329,7 @@ to the condition indicated by .IR stat . Used after .BR callrpc (). -.LP +.PP .nf .BI "clnt_perror(CLIENT *" clnt ", char *" s ); .fi @@ -342,7 +342,7 @@ The message is prepended with string and a colon. Used after .BR clnt_call (). -.LP +.PP .nf .BI "char *clnt_spcreateerror(char *" s ); .fi @@ -352,7 +352,7 @@ Like except that it returns a string instead of printing to the standard error. .IP Bugs: returns pointer to static data that is overwritten on each call. -.LP +.PP .nf .BI "char *clnt_sperrno(enum clnt_stat " stat ); .fi @@ -380,7 +380,7 @@ and .BR clnt_sperrno () returns pointer to static data, but the result will not get overwritten on each call. -.LP +.PP .nf .BI "char *clnt_sperror(CLIENT *" rpch ", char *" s ); .fi @@ -392,7 +392,7 @@ except that (like it returns a string instead of printing to standard error. .IP Bugs: returns pointer to static data that is overwritten on each call. -.LP +.PP .nf .BI "CLIENT *clntraw_create(unsigned long " prognum \ ", unsigned long " versnum ); @@ -409,7 +409,7 @@ corresponding RPC server should live in the same address space; see This allows simulation of RPC and acquisition of RPC overheads, such as round trip times, without any kernel interference. This routine returns NULL if it fails. -.LP +.PP .nf .BI "CLIENT *clnttcp_create(struct sockaddr_in *" addr , .BI " unsigned long " prognum ", unsigned long " versnum , @@ -445,7 +445,7 @@ and .IR recvsz ; values of zero choose suitable defaults. This routine returns NULL if it fails. -.LP +.PP .nf .BI "CLIENT *clntudp_create(struct sockaddr_in *" addr , .BI " unsigned long " prognum ", unsigned long " versnum , @@ -480,7 +480,7 @@ The total time for the call to time out is specified by Warning: since UDP-based RPC messages can hold only up to 8 Kbytes of encoded data, this transport cannot be used for procedures that take large arguments or return huge results. -.LP +.PP .nf .BI "CLIENT *clntudp_bufcreate(struct sockaddr_in *" addr , .BI " unsigned long " prognum ", unsigned long " versnum , @@ -515,7 +515,7 @@ The total time for the call to time out is specified by .IP This allows the user to specify the maximum packet size for sending and receiving UDP-based RPC messages. -.LP +.PP .nf .BI "void get_myaddress(struct sockaddr_in *" addr ); .fi @@ -526,7 +526,7 @@ without consulting the library routines that deal with .IR /etc/hosts . The port number is always set to .BR htons(PMAPPORT) . -.LP +.PP .nf .BI "struct pmaplist *pmap_getmaps(struct sockaddr_in *" addr ); .fi @@ -540,7 +540,7 @@ This routine can return NULL. The command .IR "rpcinfo\ \-p" uses this routine. -.LP +.PP .nf .BI "unsigned short pmap_getport(struct sockaddr_in *" addr , .BI " unsigned long " prognum ", unsigned long " versnum , @@ -569,7 +569,7 @@ service. In the latter case, the global variable .I rpc_createerr contains the RPC status. -.LP +.PP .nf .BI "enum clnt_stat pmap_rmtcall(struct sockaddr_in *" addr , .BI " unsigned long " prognum ", unsigned long " versnum , @@ -597,7 +597,7 @@ and This procedure should be used for a \(lqping\(rq and nothing else. See also .BR clnt_broadcast (). -.LP +.PP .nf .BI "bool_t pmap_set(unsigned long " prognum ", unsigned long " versnum , .BI " unsigned int " protocol ", unsigned short " port ); @@ -621,7 +621,7 @@ or This routine returns one if it succeeds, zero otherwise. Automatically done by .BR svc_register (). -.LP +.PP .nf .BI "bool_t pmap_unset(unsigned long " prognum ", unsigned long " versnum ); .fi @@ -636,7 +636,7 @@ on the machine's .B portmap service. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "int registerrpc(unsigned long " prognum ", unsigned long " versnum , .BI " unsigned long " procnum ", char *(*" procname ")(char *)," @@ -666,7 +666,7 @@ Warning: remote procedures registered in this form are accessed using the UDP/IP transport; see .BR svcudp_create () for restrictions. -.LP +.PP .nf .BI "struct rpc_createerr " rpc_createerr ; .fi @@ -676,7 +676,7 @@ that does not succeed. Use the routine .BR clnt_pcreateerror () to print the reason why. -.LP +.PP .nf .BI "void svc_destroy(SVCXPRT *" xprt ); .fi @@ -690,7 +690,7 @@ itself. Use of .I xprt is undefined after calling this routine. -.LP +.PP .nf .BI "fd_set " svc_fdset ; .fi @@ -707,7 +707,7 @@ This variable is read-only (do not pass its address to yet it may change after calls to .BR svc_getreqset () or any creation routines. -.LP +.PP .nf .BI "int " svc_fds ; .fi @@ -717,7 +717,7 @@ Similar to but limited to 32 file descriptors. This interface is obsoleted by .BR svc_fdset . -.LP +.PP .nf .BI "svc_freeargs(SVCXPRT *" xprt ", xdrproc_t " inproc ", char *" in ); .fi @@ -727,7 +727,7 @@ system when it decoded the arguments to a service procedure using .BR svc_getargs (). This routine returns 1 if the results were successfully freed, and zero otherwise. -.LP +.PP .nf .BI "svc_getargs(SVCXPRT *" xprt ", xdrproc_t " inproc ", char *" in ); .fi @@ -741,7 +741,7 @@ is the address where the arguments will be placed; .I inproc is the XDR routine used to decode the arguments. This routine returns one if decoding succeeds, and zero otherwise. -.LP +.PP .nf .BI "struct sockaddr_in *svc_getcaller(SVCXPRT *" xprt ); .fi @@ -749,7 +749,7 @@ This routine returns one if decoding succeeds, and zero otherwise. The approved way of getting the network address of the caller of a procedure associated with the RPC service transport handle, .IR xprt . -.LP +.PP .nf .BI "void svc_getreqset(fd_set *" rdfds ); .fi @@ -766,7 +766,7 @@ is the resultant read file descriptor bit mask. The routine returns when all sockets associated with the value of .I rdfds have been serviced. -.LP +.PP .nf .BI "void svc_getreq(int " rdfds ); .fi @@ -776,7 +776,7 @@ Similar to but limited to 32 file descriptors. This interface is obsoleted by .BR svc_getreqset (). -.LP +.PP .nf .BI "bool_t svc_register(SVCXPRT *" xprt ", unsigned long " prognum , .BI " unsigned long " versnum , @@ -822,7 +822,7 @@ dispatch(struct svc_req *request, SVCXPRT *xprt); The .BR svc_register () routine returns one if it succeeds, and zero otherwise. -.LP +.PP .nf .B "void svc_run(void);" .fi @@ -835,7 +835,7 @@ when one arrives. This procedure is usually waiting for a .BR select (2) system call to return. -.LP +.PP .nf .BI "bool_t svc_sendreply(SVCXPRT *" xprt ", xdrproc_t " outproc \ ", char *" out ); @@ -851,7 +851,7 @@ is the XDR routine which is used to encode the results; and .I out is the address of the results. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "void svc_unregister(unsigned long " prognum ", unsigned long " versnum ); .fi @@ -861,14 +861,14 @@ Remove all mapping of the double to dispatch routines, and of the triple .RI [ prognum , versnum , * ] to port number. -.LP +.PP .nf .BI "void svcerr_auth(SVCXPRT *" xprt ", enum auth_stat " why ); .fi .IP Called by a service dispatch routine that refuses to perform a remote procedure call due to an authentication error. -.LP +.PP .nf .BI "void svcerr_decode(SVCXPRT *" xprt ); .fi @@ -877,21 +877,21 @@ Called by a service dispatch routine that cannot successfully decode its parameters. See also .BR svc_getargs (). -.LP +.PP .nf .BI "void svcerr_noproc(SVCXPRT *" xprt ); .fi .IP Called by a service dispatch routine that does not implement the procedure number that the caller requests. -.LP +.PP .nf .BI "void svcerr_noprog(SVCXPRT *" xprt ); .fi .IP Called when the desired program is not registered with the RPC package. Service implementors usually do not need this routine. -.LP +.PP .nf .BI "void svcerr_progvers(SVCXPRT *" xprt ); .fi @@ -899,7 +899,7 @@ Service implementors usually do not need this routine. Called when the desired version of a program is not registered with the RPC package. Service implementors usually do not need this routine. -.LP +.PP .nf .BI "void svcerr_systemerr(SVCXPRT *" xprt ); .fi @@ -908,7 +908,7 @@ Called by a service dispatch routine when it detects a system error not covered by any particular protocol. For example, if a service can no longer allocate storage, it may call this routine. -.LP +.PP .nf .BI "void svcerr_weakauth(SVCXPRT *" xprt ); .fi @@ -917,7 +917,7 @@ Called by a service dispatch routine that refuses to perform a remote procedure call due to insufficient authentication parameters. The routine calls .BR "svcerr_auth(xprt, AUTH_TOOWEAK)" . -.LP +.PP .nf .BI "SVCXPRT *svcfd_create(int " fd ", unsigned int " sendsize , .BI " unsigned int " recvsize ); @@ -931,7 +931,7 @@ and .I recvsize indicate sizes for the send and receive buffers. If they are zero, a reasonable default is chosen. -.LP +.PP .nf .BI "SVCXPRT *svcraw_create(void);" .fi @@ -944,7 +944,7 @@ so the corresponding RPC client should live in the same address space; see This routine allows simulation of RPC and acquisition of RPC overheads (such as round trip times), without any kernel interference. This routine returns NULL if it fails. -.LP +.PP .nf .BI "SVCXPRT *svctcp_create(int " sock ", unsigned int " send_buf_size , .BI " unsigned int " recv_buf_size ); @@ -968,7 +968,7 @@ This routine returns NULL if it fails. Since TCP-based RPC uses buffered I/O, users may specify the size of buffers; values of zero choose suitable defaults. -.LP +.PP .nf .BI "SVCXPRT *svcudp_bufcreate(int " sock ", unsigned int " sendsize , .BI " unsigned int " recosize ); @@ -992,7 +992,7 @@ This routine returns NULL if it fails. .IP This allows the user to specify the maximum packet size for sending and receiving UDP-based RPC messages. -.LP +.PP .nf .BI "SVCXPRT *svcudp_create(int " sock ); .fi @@ -1001,7 +1001,7 @@ This call is equivalent to .I svcudp_bufcreate(sock,SZ,SZ) for some default size .IR SZ . -.LP +.PP .nf .BI "bool_t xdr_accepted_reply(XDR *" xdrs ", struct accepted_reply *" ar ); .fi @@ -1009,7 +1009,7 @@ for some default size Used for encoding RPC reply messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. -.LP +.PP .nf .BI "bool_t xdr_authunix_parms(XDR *" xdrs ", struct authunix_parms *" aupp ); .fi @@ -1018,7 +1018,7 @@ Used for describing UNIX credentials. This routine is useful for users who wish to generate these credentials without using the RPC authentication package. -.LP +.PP .nf .BI "void xdr_callhdr(XDR *" xdrs ", struct rpc_msg *" chdr ); .fi @@ -1026,7 +1026,7 @@ authentication package. Used for describing RPC call header messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. -.LP +.PP .nf .BI "bool_t xdr_callmsg(XDR *" xdrs ", struct rpc_msg *" cmsg ); .fi @@ -1034,7 +1034,7 @@ RPC-style messages without using the RPC package. Used for describing RPC call messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. -.LP +.PP .nf .BI "bool_t xdr_opaque_auth(XDR *" xdrs ", struct opaque_auth *" ap ); .fi @@ -1042,7 +1042,7 @@ messages without using the RPC package. Used for describing RPC authentication information messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. -.LP +.PP .nf .BI "bool_t xdr_pmap(XDR *" xdrs ", struct pmap *" regs ); .fi @@ -1054,7 +1054,7 @@ This routine is useful for users who wish to generate these parameters without using the .B pmap interface. -.LP +.PP .nf .BI "bool_t xdr_pmaplist(XDR *" xdrs ", struct pmaplist **" rp ); .fi @@ -1064,7 +1064,7 @@ This routine is useful for users who wish to generate these parameters without using the .B pmap interface. -.LP +.PP .nf .BI "bool_t xdr_rejected_reply(XDR *" xdrs ", struct rejected_reply *" rr ); .fi @@ -1072,7 +1072,7 @@ interface. Used for describing RPC reply messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. -.LP +.PP .nf .BI "bool_t xdr_replymsg(XDR *" xdrs ", struct rpc_msg *" rmsg ); .fi @@ -1080,7 +1080,7 @@ RPC-style messages without using the RPC package. Used for describing RPC reply messages. This routine is useful for users who wish to generate RPC style messages without using the RPC package. -.LP +.PP .nf .BI "void xprt_register(SVCXPRT *" xprt ); .fi @@ -1090,7 +1090,7 @@ they should register themselves with the RPC service package. This routine modifies the global variable .IR svc_fds . Service implementors usually do not need this routine. -.LP +.PP .nf .BI "void xprt_unregister(SVCXPRT *" xprt ); .fi diff --git a/man3/rtime.3 b/man3/rtime.3 index 4cd71a6b22..a163811123 100644 --- a/man3/rtime.3 +++ b/man3/rtime.3 @@ -22,13 +22,13 @@ rtime \- get time from a remote machine .SH DESCRIPTION This function uses the Time Server Protocol as described in RFC\ 868 to obtain the time from a remote machine. -.LP +.PP The Time Server Protocol gives the time in seconds since 00:00:00 UTC, 1 Jan 1900, and this function subtracts the appropriate constant in order to convert the result to seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC). -.LP +.PP When .I timeout is non-NULL, the udp/time socket (port 37) is used. @@ -68,14 +68,14 @@ T} Thread safety MT-Safe .TE .SH NOTES Only IPv4 is supported. -.LP +.PP Some .I in.timed versions support only TCP. Try the example program with .I use_tcp set to 1. -.LP +.PP Libc5 uses the prototype .nf diff --git a/man3/scandir.3 b/man3/scandir.3 index 06b0e20dba..3dc4f16e77 100644 --- a/man3/scandir.3 +++ b/man3/scandir.3 @@ -126,7 +126,7 @@ function \fIcompar\fP(), and collected in array \fInamelist\fP which is allocated via .BR malloc (3). If \fIfilter\fP is NULL, all entries are selected. -.LP +.PP The .BR alphasort () and diff --git a/man3/setlogmask.3 b/man3/setlogmask.3 index 1be0849120..4633c019e2 100644 --- a/man3/setlogmask.3 +++ b/man3/setlogmask.3 @@ -40,13 +40,13 @@ Logging is enabled for the priorities that have the corresponding bit set in .IR mask . The initial mask is such that logging is enabled for all priorities. -.LP +.PP The .BR setlogmask () function sets this logmask for the calling process, and returns the previous mask. If the mask argument is 0, the current logmask is not modified. -.LP +.PP The eight priorities are .BR LOG_EMERG , .BR LOG_ALERT , diff --git a/man3/shm_open.3 b/man3/shm_open.3 index 7624b4404b..f9cb8f0c21 100644 --- a/man3/shm_open.3 +++ b/man3/shm_open.3 @@ -50,7 +50,7 @@ The function performs the converse operation, removing an object previously created by .BR shm_open (). -.LP +.PP The operation of .BR shm_open () is analogous to that of @@ -71,7 +71,7 @@ followed by one or more characters, none of which are slashes. .\" case the subdirectory must exist under /dev/shm, and allow the .\" required permissions if a user wants to create a shared memory .\" object in that subdirectory. -.LP +.PP .I oflag is a bit mask created by ORing together exactly one of .B O_RDONLY @@ -127,10 +127,10 @@ does not exist, are performed atomically. .TP .B O_TRUNC If the shared memory object already exists, truncate it to zero bytes. -.LP +.PP Definitions of these flag values can be obtained by including .IR <fcntl.h> . -.LP +.PP On successful completion .BR shm_open () returns a new file descriptor referring to the shared memory object. @@ -263,7 +263,7 @@ T} Thread safety MT-Safe locale .sp 1 .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008. -.LP +.PP POSIX.1-2001 says that the group ownership of a newly created shared memory object is set to either the calling process's effective group ID or "a system default group ID". @@ -272,7 +272,7 @@ may be set to either the calling process's effective group ID or, if the object is visible in the filesystem, the group ID of the parent directory. .SH NOTES -.LP +.PP POSIX leaves the behavior of the combination of .B O_RDONLY and @@ -280,7 +280,7 @@ and unspecified. On Linux, this will successfully truncate an existing shared memory object\(emthis may not be so on other UNIX systems. -.LP +.PP The POSIX shared memory object implementation on Linux makes use of a dedicated .BR tmpfs (5) diff --git a/man3/sigpause.3 b/man3/sigpause.3 index df5eeb2156..c52e0f2afc 100644 --- a/man3/sigpause.3 +++ b/man3/sigpause.3 @@ -38,7 +38,7 @@ Don't use this function. Use .BR sigsuspend (2) instead. -.LP +.PP The function .BR sigpause () is designed to wait for some signal. diff --git a/man3/statvfs.3 b/man3/statvfs.3 index 1059805621..7252c6c88b 100644 --- a/man3/statvfs.3 +++ b/man3/statvfs.3 @@ -118,7 +118,7 @@ Writes are synched to the filesystem immediately (see the description of .B O_SYNC in .BR open (2)). -.LP +.PP It is unspecified whether all members of the returned struct have meaningful values on all filesystems. .PP diff --git a/man3/stdio_ext.3 b/man3/stdio_ext.3 index afbf6849c8..e61cd55b29 100644 --- a/man3/stdio_ext.3 +++ b/man3/stdio_ext.3 @@ -56,46 +56,46 @@ Solaris introduced routines to allow portable access to the internals of the .I FILE structure, and glibc also implemented these. -.LP +.PP The .BR __fbufsize () function returns the size of the buffer currently used by the given stream. -.LP +.PP The .BR __fpending () function returns the number of bytes in the output buffer. For wide-oriented streams the unit is wide characters. This function is undefined on buffers in reading mode, or opened read-only. -.LP +.PP The .BR __flbf () function returns a nonzero value if the stream is line-buffered, and zero otherwise. -.LP +.PP The .BR __freadable () function returns a nonzero value if the stream allows reading, and zero otherwise. -.LP +.PP The .BR __fwritable () function returns a nonzero value if the stream allows writing, and zero otherwise. -.LP +.PP The .BR __freading () function returns a nonzero value if the stream is read-only, or if the last operation on the stream was a read operation, and zero otherwise. -.LP +.PP The .BR __fwriting () function returns a nonzero value if the stream is write-only (or append-only), or if the last operation on the stream was a write operation, and zero otherwise. -.LP +.PP The .BR __fsetlocking () function can be used to select the desired type of locking on the stream. @@ -119,13 +119,13 @@ will not do locking until the state is reset to .B FSETLOCKING_QUERY Don't change the type of locking. (Only return it.) -.LP +.PP The .BR _flushlbf () function flushes all line-buffered streams. (Presumably so that output to a terminal is forced out, say before reading keyboard input.) -.LP +.PP The .BR __fpurge () function discards the contents of the stream's buffer. diff --git a/man3/strfmon.3 b/man3/strfmon.3 index 689d2bc138..37f0eea237 100644 --- a/man3/strfmon.3 +++ b/man3/strfmon.3 @@ -98,20 +98,20 @@ Omit the currency symbol. .B \- Left justify all fields. The default is right justification. -.LP +.PP Next, there may be a field width: a decimal digit string specifying a minimum field width in bytes. The default is 0. A result smaller than this width is padded with spaces (on the left, unless the left-justify flag was given). -.LP +.PP Next, there may be a left precision of the form "#" followed by a decimal digit string. If the number of digits left of the radix character is smaller than this, the representation is padded on the left with the numeric fill character. Grouping characters are not counted in this field width. -.LP +.PP Next, there may be a right precision of the form "." followed by a decimal digit string. The amount being formatted is rounded to @@ -126,7 +126,7 @@ If the right precision is 0, no radix character is printed. .BR LC_MONETARY , and may differ from that specified by .BR LC_NUMERIC .) -.LP +.PP Finally, the conversion specification must be ended with a conversion character. The three conversion characters are diff --git a/man3/strftime.3 b/man3/strftime.3 index 7da2a13703..a1b90e2f82 100644 --- a/man3/strftime.3 +++ b/man3/strftime.3 @@ -414,7 +414,7 @@ returns 0, and the contents of the array are undefined. .\" would return .\" .I max .\" if the array was too small.) -.LP +.PP Note that the return value 0 does not necessarily indicate an error. For example, in many locales .B %p diff --git a/man3/strptime.3 b/man3/strptime.3 index 8e8316ba11..3e50c3d23d 100644 --- a/man3/strptime.3 +++ b/man3/strptime.3 @@ -217,13 +217,13 @@ range 00-68 refer to years in the twenty-first century (2000-2068). .TP .B %Y The year, including century (for example, 1991). -.LP +.PP Some field descriptors can be modified by the E or O modifier characters to indicate that an alternative format or specification should be used. If the alternative format or specification does not exist in the current locale, the unmodified field descriptor is used. -.LP +.PP The E modifier specifies that the input string may contain alternative locale-dependent versions of the date and time representation: .TP @@ -246,7 +246,7 @@ The offset from .TP .B %EY The full alternative year representation. -.LP +.PP The O modifier specifies that the numerical input may be in an alternative locale-dependent format: .TP @@ -314,7 +314,7 @@ T} Thread safety MT-Safe env locale .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SUSv2. .SH NOTES -.LP +.PP In principle, this function does not initialize .I tm but @@ -389,7 +389,7 @@ An RFC-822/ISO 8601 standard timezone specification. .TP .B %Z The timezone name. -.LP +.PP Similarly, because of GNU extensions to .BR strftime (3), .B %k @@ -409,7 +409,7 @@ Finally .B %s The number of seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC). Leap seconds are not counted unless leap second support is available. -.LP +.PP The glibc implementation does not require whitespace between two field descriptors. .SH EXAMPLE diff --git a/man3/strtod.3 b/man3/strtod.3 index 6bce66ef33..b283ed651b 100644 --- a/man3/strtod.3 +++ b/man3/strtod.3 @@ -87,7 +87,7 @@ optional leading white space as recognized by an optional plus (\(aq+\(aq) or minus sign (\(aq\-\(aq) and then either (i) a decimal number, or (ii) a hexadecimal number, or (iii) an infinity, or (iv) a NAN (not-a-number). -.LP +.PP A .I "decimal number" consists of a nonempty sequence of decimal digits @@ -96,7 +96,7 @@ usually \(aq.\(aq), optionally followed by a decimal exponent. A decimal exponent consists of an \(aqE\(aq or \(aqe\(aq, followed by an optional plus or minus sign, followed by a nonempty sequence of decimal digits, and indicates multiplication by a power of 10. -.LP +.PP A .I "hexadecimal number" consists of a "0x" or "0X" followed by a nonempty sequence of @@ -107,11 +107,11 @@ consists of a \(aqP\(aq or \(aqp\(aq, followed by an optional plus or minus sign, followed by a nonempty sequence of decimal digits, and indicates multiplication by a power of 2. At least one of radix character and binary exponent must be present. -.LP +.PP An .I infinity is either "INF" or "INFINITY", disregarding case. -.LP +.PP A .I NAN is "NAN" (disregarding case) optionally followed by a string, diff --git a/man3/strtol.3 b/man3/strtol.3 index d828ebff25..34d27cd4e2 100644 --- a/man3/strtol.3 +++ b/man3/strtol.3 @@ -148,7 +148,7 @@ contains an unsupported value. .TP .B ERANGE The resulting value was out of range. -.LP +.PP The implementation may also set .IR errno to @@ -198,7 +198,7 @@ According to POSIX.1, in locales other than the "C" and "POSIX", these functions may accept other, implementation-defined numeric strings. -.LP +.PP BSD also has .PP .in +4n diff --git a/man3/strtoul.3 b/man3/strtoul.3 index 9b78e49948..7c9e4699f3 100644 --- a/man3/strtoul.3 +++ b/man3/strtoul.3 @@ -152,7 +152,7 @@ contains an unsupported value. .TP .B ERANGE The resulting value was out of range. -.LP +.PP The implementation may also set .IR errno to @@ -197,7 +197,7 @@ has a nonzero value after the call. In locales other than the "C" locale, other strings may be accepted. (For example, the thousands separator of the current locale may be supported.) -.LP +.PP BSD also has .PP .in +4n diff --git a/man3/swab.3 b/man3/swab.3 index 19cd6ba7e2..f73c168d24 100644 --- a/man3/swab.3 +++ b/man3/swab.3 @@ -52,7 +52,7 @@ exchanging adjacent even and odd bytes. This function is used to exchange data between machines that have different low/high byte ordering. -.LP +.PP This function does nothing when .I n is negative. diff --git a/man3/sysconf.3 b/man3/sysconf.3 index 11325a2e0a..90d686672c 100644 --- a/man3/sysconf.3 +++ b/man3/sysconf.3 @@ -37,13 +37,13 @@ sysconf \- get configuration information at run time POSIX allows an application to test at compile or run time whether certain options are supported, or what the value is of certain configurable constants or limits. -.LP +.PP At compile time this is done by including .I <unistd.h> and/or .I <limits.h> and testing the value of certain macros. -.LP +.PP At run time, one can ask for numerical values using the present function .BR sysconf (). One can ask for numerical values that may depend @@ -53,12 +53,12 @@ and .BR pathconf (3). One can ask for string values using .BR confstr (3). -.LP +.PP The values obtained from these functions are system configuration constants. They do not change during the lifetime of a process. .\" except that sysconf(_SC_OPEN_MAX) may change answer after a call .\" to setrlimit( ) which changes the RLIMIT_NOFILE soft limit -.LP +.PP For options, typically, there is a constant .B _POSIX_FOO that may be defined in @@ -81,7 +81,7 @@ argument will be .BR _SC_FOO . For a list of options, see .BR posixoptions (7). -.LP +.PP For variables or limits, typically, there is a constant .BR _FOO , maybe defined in @@ -106,7 +106,7 @@ We give the name of the variable, the name of the .BR sysconf () argument used to inquire about its value, and a short description. -.LP +.PP First, the POSIX.1 compatible values. .\" [for the moment: only the things that are unconditionally present] .\" .TP diff --git a/man3/syslog.3 b/man3/syslog.3 index e4cf4d8226..82a0b1f8d7 100644 --- a/man3/syslog.3 +++ b/man3/syslog.3 @@ -268,7 +268,7 @@ informational message .TP .B LOG_DEBUG debug-level message -.LP +.PP The function .BR setlogmask (3) can be used to restrict logging to specified levels only. @@ -347,7 +347,7 @@ is changed, may start prepending the changed string, and if the string it points to ceases to exist, the results are undefined. Most portable is to use a string constant. -.LP +.PP Never pass a string with user-supplied data as a format, use the following instead: .nf diff --git a/man3/tcgetpgrp.3 b/man3/tcgetpgrp.3 index 2bcc1904d8..3d2f0eed23 100644 --- a/man3/tcgetpgrp.3 +++ b/man3/tcgetpgrp.3 @@ -39,7 +39,7 @@ terminal associated to .IR fd , which must be the controlling terminal of the calling process. .\" The process itself may be a background process. -.LP +.PP The function .BR tcsetpgrp () makes the process group with process group ID @@ -52,7 +52,7 @@ Moreover, .I pgrp must be a (nonempty) process group belonging to the same session as the calling process. -.LP +.PP If .BR tcsetpgrp () is called by a member of a background process group in its session, @@ -76,7 +76,7 @@ does not refer to the controlling terminal of the calling process, \-1 is returned, and .I errno is set appropriately. -.LP +.PP When successful, .BR tcsetpgrp () returns 0. diff --git a/man3/tempnam.3 b/man3/tempnam.3 index cc91268410..8d50213399 100644 --- a/man3/tempnam.3 +++ b/man3/tempnam.3 @@ -149,12 +149,12 @@ when the program is not set-user-ID. On SVr4, the directory used under \fBd)\fP is .I /tmp (and this is what glibc does). -.LP +.PP Because it dynamically allocates memory used to return the pathname, .BR tempnam () is reentrant, and thus thread safe, unlike .BR tmpnam (3). -.LP +.PP The .BR tempnam () function generates a different string each time it is called, @@ -167,7 +167,7 @@ If it is called more than .B TMP_MAX times, the behavior is implementation defined. -.LP +.PP .BR tempnam () uses at most the first five bytes from .IR pfx . diff --git a/man3/termios.3 b/man3/termios.3 index 0b96825ee0..0917cb10e0 100644 --- a/man3/termios.3 +++ b/man3/termios.3 @@ -88,7 +88,7 @@ Feature Test Macro Requirements for glibc (see The termios functions describe a general terminal interface that is provided to control asynchronous communications ports. .SS The termios structure -.LP +.PP Many of the functions described here have a \fItermios_p\fP argument that is a pointer to a \fItermios\fP structure. This structure contains at least the following members: @@ -644,13 +644,13 @@ Recognized when and .B IEXTEN are set, and then not passed as input. -.LP +.PP An individual terminal special character can be disabled by setting the value of the corresponding .I c_cc element to .BR _POSIX_VDISABLE . -.LP +.PP The above symbolic subscript values are all different, except that .BR VTIME , .B VMIN @@ -675,7 +675,7 @@ stores them in the \fItermios\fP structure referenced by This function may be invoked from a background process; however, the terminal attributes may be subsequently changed by a foreground process. -.LP +.PP .BR tcsetattr () sets the parameters associated with the terminal (unless support is required from the underlying hardware that is not available) from the @@ -834,7 +834,7 @@ in noncanonical mode to return either 0, or \-1 with set to .BR EAGAIN . .SS Raw mode -.LP +.PP .BR cfmakeraw () sets the terminal to something like the "raw" mode of the old Version 7 terminal driver: @@ -852,7 +852,7 @@ The terminal attributes are set as follows: termios_p\->c_cflag |= CS8; .fi .SS Line control -.LP +.PP .BR tcsendbreak () transmits a continuous stream of zero-valued bits for a specific duration, if the terminal is using asynchronous serial data @@ -861,16 +861,16 @@ If \fIduration\fP is zero, it transmits zero-valued bits for at least 0.25 seconds, and not more that 0.5 seconds. If \fIduration\fP is not zero, it sends zero-valued bits for some implementation-defined length of time. -.LP +.PP If the terminal is not using asynchronous serial data transmission, .BR tcsendbreak () returns without taking any action. -.LP +.PP .BR tcdrain () waits until all output written to the object referred to by .I fd has been transmitted. -.LP +.PP .BR tcflush () discards data written to the object referred to by .I fd @@ -884,7 +884,7 @@ flushes data written but not transmitted. .IP \fBTCIOFLUSH\fP flushes both data received but not read, and data written but not transmitted. -.LP +.PP .BR tcflow () suspends transmission or reception of data on the object referred to by .IR fd , @@ -900,7 +900,7 @@ transmitting data to the system. .IP \fBTCION\fP transmits a START character, which starts the terminal device transmitting data to the system. -.LP +.PP The default on open of a terminal file is that neither its input nor its output is suspended. .SS Line speed @@ -914,15 +914,15 @@ is successfully called. 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). -.LP +.PP The input and output baud rates are stored in the \fItermios\fP structure. -.LP +.PP .BR cfgetospeed () returns the output baud rate stored in the \fItermios\fP structure pointed to by .IR termios_p . -.LP +.PP .BR cfsetospeed () sets the output baud rate stored in the \fItermios\fP structure pointed to by \fItermios_p\fP to \fIspeed\fP, which must be one of these constants: @@ -958,10 +958,10 @@ Normally, this will disconnect the line. \fBCBAUDEX\fP is a mask for the speeds beyond those defined in POSIX.1 (57600 and above). Thus, \fBB57600\fP & \fBCBAUDEX\fP is nonzero. -.LP +.PP .BR cfgetispeed () returns the input baud rate stored in the \fItermios\fP structure. -.LP +.PP .BR cfsetispeed () sets the input baud rate stored in the \fItermios\fP structure to .IR speed , @@ -969,22 +969,22 @@ which must be specified as one of the \fBBnnn\fP constants listed above for .BR cfsetospeed (). If the input baud rate is set to zero, the input baud rate will be equal to the output baud rate. -.LP +.PP .BR cfsetspeed () is a 4.4BSD extension. It takes the same arguments as .BR cfsetispeed (), and sets both input and output speed. .SH RETURN VALUE -.LP +.PP .BR cfgetispeed () returns the input baud rate stored in the \fItermios\fP structure. -.LP +.PP .BR cfgetospeed () returns the output baud rate stored in the \fItermios\fP structure. -.LP +.PP All other functions return: .IP 0 on success. @@ -992,7 +992,7 @@ on success. on failure and set .I errno to indicate the error. -.LP +.PP Note that .BR tcsetattr () returns success if \fIany\fP of the requested changes could be @@ -1060,7 +1060,7 @@ UNIX\ V7 and several later systems have a list of baud rates where after the fourteen values B0, ..., B9600 one finds the two constants EXTA, EXTB ("External A" and "External B"). Many systems extend the list with much higher baud rates. -.LP +.PP The effect of a nonzero \fIduration\fP with .BR tcsendbreak () varies. diff --git a/man3/tmpfile.3 b/man3/tmpfile.3 index 0c7796fa54..e5b2a92b37 100644 --- a/man3/tmpfile.3 +++ b/man3/tmpfile.3 @@ -96,7 +96,7 @@ an error message may be written to .I stdout if the stream cannot be opened. -.LP +.PP The standard does not specify the directory that .BR tmpfile () will use. diff --git a/man3/tmpnam.3 b/man3/tmpnam.3 index 2b9ce3c6f4..cf73068ef5 100644 --- a/man3/tmpnam.3 +++ b/man3/tmpnam.3 @@ -82,7 +82,7 @@ pointed to by and the value .I s is returned in case of success. -.LP +.PP The created pathname has a directory prefix .IR P_tmpdir . (Both @@ -144,7 +144,7 @@ If it is called more than .B TMP_MAX times, the behavior is implementation defined. -.LP +.PP Although these functions generate names that are difficult to guess, it is nevertheless possible that between the time that the pathname is returned and the time that the program opens it, @@ -160,7 +160,7 @@ Or better yet, use .BR mkstemp (3) or .BR tmpfile (3). -.LP +.PP Portable applications that use threads cannot call .BR tmpnam () with a NULL argument if either diff --git a/man3/ttyslot.3 b/man3/ttyslot.3 index dd6c08c7fc..61dfd2bc77 100644 --- a/man3/ttyslot.3 +++ b/man3/ttyslot.3 @@ -57,7 +57,7 @@ Glibc 2.19 and earlier: The legacy function .BR ttyslot () returns the index of the current user's entry in some file. -.LP +.PP Now "What file?" you ask. Well, let's first look at some history. .SS Ancient history @@ -77,7 +77,7 @@ indicating the sequence of line speeds to try (\(aq\-\(aq was: start trying Thus a typical line was "18\-". A hang on some line was solved by changing the \(aq1\(aq to a \(aq0\(aq, signaling init, changing back again, and signaling init again. -.LP +.PP In UNIX\ V7 the format was changed: here the second character was the argument to .BR getty (8) @@ -85,7 +85,7 @@ indicating the sequence of line speeds to try (\(aq0\(aq was: cycle through 300-1200-150-110 baud; \(aq4\(aq was for the on-line console DECwriter) while the rest of the line contained the name of the tty. Thus a typical line was "14console". -.LP +.PP Later systems have more elaborate syntax. System V-like systems have .I /etc/inittab @@ -145,7 +145,7 @@ The utmp file is found in various places on various systems, such as .IR /etc/utmp , .IR /var/adm/utmp , .IR /var/run/utmp . -.LP +.PP The glibc2 implementation of this function reads the file .BR _PATH_TTYS , defined in diff --git a/man3/tzset.3 b/man3/tzset.3 index 70e455aceb..0c665e02aa 100644 --- a/man3/tzset.3 +++ b/man3/tzset.3 @@ -231,7 +231,7 @@ T} Thread safety MT-Safe env locale .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD. .SH NOTES -.LP +.PP 4.3BSD had a function .BI "char *timezone(" zone ", " dst ) that returned the diff --git a/man3/ualarm.3 b/man3/ualarm.3 index 973e75043f..ed05113330 100644 --- a/man3/ualarm.3 +++ b/man3/ualarm.3 @@ -65,11 +65,11 @@ microseconds. The delay may be lengthened slightly by any system activity or by the time spent processing the call or by the granularity of system timers. -.LP +.PP Unless caught or ignored, the .B SIGALRM signal will terminate the process. -.LP +.PP If the .I interval argument is nonzero, further @@ -129,7 +129,7 @@ were instead typed as Programs will be more portable if they never mention .I useconds_t explicitly. -.LP +.PP The interaction of this function with other timer functions such as .BR alarm (2), @@ -143,7 +143,7 @@ other timer functions such as .BR timer_settime (2), .BR usleep (3) is unspecified. -.LP +.PP This function is obsolete. Use .BR setitimer (2) diff --git a/man3/usleep.3 b/man3/usleep.3 index 9e317ab79c..fb23931d2f 100644 --- a/man3/usleep.3 +++ b/man3/usleep.3 @@ -135,7 +135,7 @@ Use usleep(usecs); .EE .in -.LP +.PP The interaction of this function with the .B SIGALRM signal, and with other timer functions such as diff --git a/man3/wordexp.3 b/man3/wordexp.3 index 5189206d73..3df86d8532 100644 --- a/man3/wordexp.3 +++ b/man3/wordexp.3 @@ -73,7 +73,7 @@ is sometimes (depending on see below) used to indicate the number of initial elements in the .I we_wordv array that should be filled with NULLs. -.LP +.PP The function .BR wordfree () frees the allocated memory again. @@ -91,7 +91,7 @@ parameters. In particular, there must not be any unescaped newline or |, &, ;, <, >, (, ), {, } characters outside a command substitution or parameter substitution context. -.LP +.PP If the argument .I s contains a word that starts with an unquoted comment character #, @@ -104,10 +104,10 @@ variable substitution (replacing $FOO by the value of the environment variable FOO), command substitution (replacing $(command) or \`command\` by the output of command), arithmetic expansion, field splitting, wildcard expansion, quote removal. -.LP +.PP The result of expansion of special parameters ($@, $*, $#, $?, $\-, $$, $!, $0) is unspecified. -.LP +.PP Field splitting is done using the environment variable $IFS. If it is not set, the field separators are space, tab and newline. .SS The output array @@ -223,7 +223,7 @@ POSIX.1-2001, POSIX.1-2008. .SH EXAMPLE The output of the following example program is approximately that of "ls [a-c]*.c". -.LP +.PP .nf #include <stdio.h> #include <stdlib.h> diff --git a/man3/xcrypt.3 b/man3/xcrypt.3 index 22556dfb20..766555efe7 100644 --- a/man3/xcrypt.3 +++ b/man3/xcrypt.3 @@ -37,7 +37,7 @@ Both other functions described here use this function to turn their argument .I passwd into a DES key. -.LP +.PP The .BR xencrypt () function takes the ASCII character string @@ -54,7 +54,7 @@ and outputs the result again in as a hex string .\" (over the alphabet 0123456789abcdef) of the same length. -.LP +.PP The .BR xdecrypt () function performs the converse operation. diff --git a/man3/xdr.3 b/man3/xdr.3 index 87dc013449..9644ba42dd 100644 --- a/man3/xdr.3 +++ b/man3/xdr.3 @@ -12,7 +12,7 @@ .SH NAME xdr \- library routines for external data representation .SH SYNOPSIS AND DESCRIPTION -.LP +.PP These routines allow C programmers to describe arbitrary data structures in a machine-independent fashion. Data for remote procedure calls are transmitted using these @@ -29,12 +29,12 @@ and make use of the following types: .BI "typedef bool_t (*" xdrproc_t ") (XDR *, void *,...);" .fi .in -.LP +.PP For the declaration of the .I XDR type, see .IR <rpc/xdr.h> . -.LP +.PP .nf .BI "bool_t xdr_array(XDR *" xdrs ", char **" arrp ", unsigned int *" sizep , .BI " unsigned int " maxsize ", unsigned int " elsize , @@ -60,7 +60,7 @@ is an XDR filter that translates between the array elements' C form, and their external representation. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_bool(XDR *" xdrs ", bool_t *" bp ); .fi @@ -71,7 +71,7 @@ and their external representations. When encoding data, this filter produces values of either one or zero. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_bytes(XDR *" xdrs ", char **" sp ", unsigned int *" sizep , .BI " unsigned int " maxsize ); @@ -88,7 +88,7 @@ string is located at address strings cannot be longer than .IR maxsize . This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_char(XDR *" xdrs ", char *" cp ); .fi @@ -103,7 +103,7 @@ consider .BR xdr_opaque () or .BR xdr_string (). -.LP +.PP .nf .BI "void xdr_destroy(XDR *" xdrs ); .fi @@ -117,7 +117,7 @@ Using after invoking .BR xdr_destroy () is undefined. -.LP +.PP .nf .BI "bool_t xdr_double(XDR *" xdrs ", double *" dp ); .fi @@ -126,7 +126,7 @@ A filter primitive that translates between C .I double precision numbers and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_enum(XDR *" xdrs ", enum_t *" ep ); .fi @@ -135,7 +135,7 @@ A filter primitive that translates between C .IR enum s (actually integers) and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_float(XDR *" xdrs ", float *" fp ); .fi @@ -144,7 +144,7 @@ A filter primitive that translates between C .IR float s and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "void xdr_free(xdrproc_t " proc ", char *" objp ); .fi @@ -157,7 +157,7 @@ Note: the pointer passed to this routine is freed, but what it points to .I is freed (recursively). -.LP +.PP .nf .BI "unsigned int xdr_getpos(XDR *" xdrs ); .fi @@ -170,7 +170,7 @@ which indicates the position of the XDR byte stream. A desirable feature of XDR streams is that simple arithmetic works with this number, although the XDR stream instances need not guarantee this. -.LP +.PP .nf .BI "long *xdr_inline(XDR *" xdrs ", int " len ); .fi @@ -190,7 +190,7 @@ may return NULL (0) if it cannot allocate a contiguous piece of a buffer. Therefore the behavior may vary among stream instances; it exists for the sake of efficiency. -.LP +.PP .nf .BI "bool_t xdr_int(XDR *" xdrs ", int *" ip ); .fi @@ -198,7 +198,7 @@ it exists for the sake of efficiency. A filter primitive that translates between C integers and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_long(XDR *" xdrs ", long *" lp ); .fi @@ -207,7 +207,7 @@ A filter primitive that translates between C .I long integers and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "void xdrmem_create(XDR *" xdrs ", char *" addr ", unsigned int " size , .BI " enum xdr_op " op ); @@ -228,7 +228,7 @@ determines the direction of the XDR stream (either .BR XDR_DECODE , or .BR XDR_FREE ). -.LP +.PP .nf .BI "bool_t xdr_opaque(XDR *" xdrs ", char *" cp ", unsigned int " cnt ); .fi @@ -241,7 +241,7 @@ is the address of the opaque object, and .I cnt is its size in bytes. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_pointer(XDR *" xdrs ", char **" objpp , .BI " unsigned int " objsize ", xdrproc_t " xdrobj ); @@ -257,7 +257,7 @@ Thus, can represent recursive data structures, such as binary trees or linked lists. -.LP +.PP .nf .BI "void xdrrec_create(XDR *" xdrs ", unsigned int " sendsize , .BI " unsigned int " recvsize ", char *" handle , @@ -300,7 +300,7 @@ record boundary information. Also, XDR streams created with different .BR xdr*_create APIs are not compatible for the same reason. -.LP +.PP .nf .BI "bool_t xdrrec_endofrecord(XDR *" xdrs ", int " sendnow ); .fi @@ -312,7 +312,7 @@ and the output buffer is optionally written out if .I sendnow is nonzero. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdrrec_eof(XDR *" xdrs ); .fi @@ -322,7 +322,7 @@ This routine can be invoked only on streams created by After consuming the rest of the current record in the stream, this routine returns one if the stream has no more input, zero otherwise. -.LP +.PP .nf .BI "bool_t xdrrec_skiprecord(XDR *" xdrs ); .fi @@ -333,7 +333,7 @@ streams created by It tells the XDR implementation that the rest of the current record in the stream's input buffer should be discarded. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_reference(XDR *" xdrs ", char **" pp ", unsigned int " size , .BI " xdrproc_t " proc ); @@ -358,7 +358,7 @@ Warning: this routine does not understand null pointers. Use .BR xdr_pointer () instead. -.LP +.PP .nf .BI "xdr_setpos(XDR *" xdrs ", unsigned int " pos ); .fi @@ -376,7 +376,7 @@ and zero otherwise. Warning: it is difficult to reposition some types of XDR streams, so this routine may fail with one type of stream and succeed with another. -.LP +.PP .nf .BI "bool_t xdr_short(XDR *" xdrs ", short *" sp ); .fi @@ -385,7 +385,7 @@ A filter primitive that translates between C .I short integers and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "void xdrstdio_create(XDR *" xdrs ", FILE *" file ", enum xdr_op " op ); .fi @@ -410,7 +410,7 @@ on the .I file stream, but never .BR fclose (3). -.LP +.PP .nf .BI "bool_t xdr_string(XDR *" xdrs ", char **" sp ", unsigned int " maxsize ); .fi @@ -423,7 +423,7 @@ Note: .I sp is the address of the string's pointer. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_u_char(XDR *" xdrs ", unsigned char *" ucp ); .fi @@ -432,7 +432,7 @@ A filter primitive that translates between .I unsigned C characters and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_u_int(XDR *" xdrs ", unsigned *" up ); .fi @@ -441,7 +441,7 @@ A filter primitive that translates between C .I unsigned integers and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_u_long(XDR *" xdrs ", unsigned long *" ulp ); .fi @@ -450,7 +450,7 @@ A filter primitive that translates between C .I "unsigned long" integers and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_u_short(XDR *" xdrs ", unsigned short *" usp ); .fi @@ -459,7 +459,7 @@ A filter primitive that translates between C .I "unsigned short" integers and their external representations. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_union(XDR *" xdrs ", int *" dscmp ", char *" unp , .BI " struct xdr_discrim *" choices , @@ -498,7 +498,7 @@ array, then the .I defaultarm procedure is called (if it is not NULL). Returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_vector(XDR *" xdrs ", char *" arrp ", unsigned int " size , .BI " unsigned int " elsize ", xdrproc_t " elproc ); @@ -521,7 +521,7 @@ is an XDR filter that translates between the array elements' C form, and their external representation. This routine returns one if it succeeds, zero otherwise. -.LP +.PP .nf .BI "bool_t xdr_void(void);" .fi @@ -529,7 +529,7 @@ This routine returns one if it succeeds, zero otherwise. This routine always returns one. It may be passed to RPC routines that require a function argument, where nothing is to be done. -.LP +.PP .nf .BI "bool_t xdr_wrapstring(XDR *" xdrs ", char **" sp ); .fi @@ -609,7 +609,7 @@ T} Thread safety MT-Safe .sp 1 .SH SEE ALSO .BR rpc (3) -.LP +.PP The following manuals: .RS eXternal Data Representation Standard: Protocol Specification diff --git a/man4/cciss.4 b/man4/cciss.4 index b982bd6a6f..b2f0729482 100644 --- a/man4/cciss.4 +++ b/man4/cciss.4 @@ -280,7 +280,7 @@ physical SCSI buses and/or fibre channel arbitrated loop, and make note of any new or removed sequential access devices or medium changers. .RE -.LP +.PP The driver will output messages indicating which devices have been added or removed and the controller, bus, target, and lun used to address each device. @@ -327,7 +327,7 @@ If that doesn't work, the device is reset. If that doesn't work, the SCSI bus is reset. .IP * If that doesn't work, the host bus adapter is reset. -.LP +.PP The .B cciss driver is a block diff --git a/man4/console_codes.4 b/man4/console_codes.4 index aa88ff5a54..78bee11593 100644 --- a/man4/console_codes.4 +++ b/man4/console_codes.4 @@ -30,31 +30,31 @@ for changing the color palette, character-set mapping, and so on. In the tabular descriptions below, the second column gives ECMA-48 or DEC mnemonics (the latter if prefixed with DEC) for the given function. Sequences without a mnemonic are neither ECMA-48 nor VT102. -.LP +.PP After all the normal output processing has been done, and a stream of characters arrives at the console driver for actual printing, the first thing that happens is a translation from the code used for processing to the code used for printing. -.LP +.PP If the console is in UTF-8 mode, then the incoming bytes are first assembled into 16-bit Unicode codes. Otherwise, each byte is transformed according to the current mapping table (which translates it to a Unicode value). See the \fBCharacter Sets\fP section below for discussion. -.LP +.PP In the normal case, the Unicode value is converted to a font index, and this is stored in video memory, so that the corresponding glyph (as found in video ROM) appears on the screen. Note that the use of Unicode (and the design of the PC hardware) allows us to use 512 different glyphs simultaneously. -.LP +.PP If the current Unicode value is a control character, or we are currently processing an escape sequence, the value will treated specially. Instead of being turned into a font index and rendered as a glyph, it may trigger cursor movement or other control functions. See the \fBLinux Console Controls\fP section below for discussion. -.LP +.PP It is generally not good practice to hard-wire terminal controls into programs. Linux supports a @@ -483,9 +483,9 @@ DC1 (0x11, \fB^Q\fP, XON) resumed transmission; .HP DC3 (0x13, \fB^S\fP, XOFF) caused VT100 to ignore (and stop transmitting) all codes except XOFF and XON. -.LP +.PP VT100-like DC1/DC3 processing may be enabled by the terminal driver. -.LP +.PP The .BR xterm (1) program (in VT100 mode) recognizes the control characters diff --git a/man4/full.4 b/man4/full.4 index ab33691bc2..7ed2552010 100644 --- a/man4/full.4 +++ b/man4/full.4 @@ -41,7 +41,7 @@ File .I /dev/full has major device number 1 and minor device number 7. -.LP +.PP Writes to the .I /dev/full device will fail with an @@ -44,7 +44,7 @@ is .B hdc and the slave is .BR hdd . -.LP +.PP General IDE block device names have the form .BI hd X\c , or @@ -68,13 +68,13 @@ Thus, the first logical partition will be \&. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions on an IDE disk. -.LP +.PP For example, .I /dev/hda refers to all of the first IDE drive in the system; and .I /dev/hdb3 refers to the third DOS "primary" partition on the second one. -.LP +.PP They are typically created by: .PP .in +4n diff --git a/man4/loop.4 b/man4/loop.4 index a7ca14e3ed..cd5fc9f498 100644 --- a/man4/loop.4 +++ b/man4/loop.4 @@ -46,7 +46,7 @@ $ \fBsudo mkfs -t ext4 /dev/loop4\fP $ \fBsudo mkdir /myloopdev\fP $ \fBsudo mount /dev/loop4 /myloopdev\fP .fi -.LP +.PP See .BR losetup (8) for another example. diff --git a/man4/mem.4 b/man4/mem.4 index 86483ad105..6ff0121ae1 100644 --- a/man4/mem.4 +++ b/man4/mem.4 @@ -31,22 +31,22 @@ mem, kmem, port \- system memory, kernel memory and system ports is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even patch) the system. -.LP +.PP Byte addresses in .IR /dev/mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned. -.LP +.PP Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present. -.LP +.PP Since Linux 2.6.26, and depending on the architecture, the .B CONFIG_STRICT_DEVMEM kernel configuration option limits the areas which can be accessed through this file. For example: on x86, RAM access is not allowed but accessing memory-mapped PCI regions is. -.LP +.PP It is typically created by: .PP .in +4n @@ -65,7 +65,7 @@ rather than physical memory is accessed. Since Linux 2.6.26, this file is available only if the .B CONFIG_DEVKMEM kernel configuration option is enabled. -.LP +.PP It is typically created by: .PP .in +4n @@ -79,7 +79,7 @@ chown root:kmem /dev/kmem is similar to .IR /dev/mem , but the I/O ports are accessed. -.LP +.PP It is typically created by: .PP .in +4n diff --git a/man4/null.4 b/man4/null.4 index 5563b3d864..871d7ea4e3 100644 --- a/man4/null.4 +++ b/man4/null.4 @@ -40,7 +40,7 @@ always return end of file (i.e., returns 0), whereas reads from .IR /dev/zero always return bytes containing zero (\(aq\e0\(aq characters). -.LP +.PP These devices are typically created by: .PP .in +4n diff --git a/man4/pts.4 b/man4/pts.4 index e78bece944..fa3ea60c09 100644 --- a/man4/pts.4 +++ b/man4/pts.4 @@ -65,7 +65,7 @@ is done using the .I devpts filesystem, that should be mounted on .IR /dev/pts . -.LP +.PP Before this UNIX 98 scheme, master pseudoterminals were called .IR /dev/ptyp0 ", ..." and slave pseudoterminals diff --git a/man4/ram.4 b/man4/ram.4 index 100d0bb725..6ac501941d 100644 --- a/man4/ram.4 +++ b/man4/ram.4 @@ -30,7 +30,7 @@ ram \- ram disk device The .I ram device is a block device to access the ram disk in raw mode. -.LP +.PP It is typically created by: .PP .in +4n diff --git a/man4/random.4 b/man4/random.4 index 0b7ee560e2..b3a1497bbf 100644 --- a/man4/random.4 +++ b/man4/random.4 @@ -31,13 +31,13 @@ has major device number 1 and minor device number 8. The file .I /dev/urandom has major device number 1 and minor device number 9. -.LP +.PP The random number generator gathers environmental noise from device drivers and other sources into an entropy pool. The generator also keeps an estimate of the number of bits of noise in the entropy pool. From this entropy pool, random numbers are created. -.LP +.PP Linux 3.17 and later provides the simpler and safer .BR getrandom (2) interface which requires no special files; diff --git a/man4/tty.4 b/man4/tty.4 index 5b6cb83285..431d0c5015 100644 --- a/man4/tty.4 +++ b/man4/tty.4 @@ -34,7 +34,7 @@ The file is a character file with major number 5 and minor number 0, usually of mode 0666 and owner.group root.tty. It is a synonym for the controlling terminal of a process, if any. -.LP +.PP In addition to the .BR ioctl (2) requests supported by the device that diff --git a/man4/ttyS.4 b/man4/ttyS.4 index 5fdd406923..5ba50225a7 100644 --- a/man4/ttyS.4 +++ b/man4/ttyS.4 @@ -29,7 +29,7 @@ ttyS \- serial terminal lines .SH DESCRIPTION .B ttyS[0\-3] are character devices for the serial terminal lines. -.LP +.PP They are typically created by: .PP .in +4n diff --git a/man4/vcs.4 b/man4/vcs.4 index 49d58f06f5..2c2d6c826f 100644 --- a/man4/vcs.4 +++ b/man4/vcs.4 @@ -35,7 +35,7 @@ is a character device with major number 7 and minor number 0, usually of mode 0644 and owner root.tty. It refers to the memory of the currently displayed virtual console terminal. -.LP +.PP .I /dev/vcs[1\-63] are character devices for virtual console terminals, they have major number 7 and minor number 1 to 63, usually diff --git a/man5/networks.5 b/man5/networks.5 index f2b2be22da..5f74775315 100644 --- a/man5/networks.5 +++ b/man5/networks.5 @@ -58,7 +58,7 @@ The trailing ".0" (for the host component of the network address) may be omitted .TP .I aliases Optional aliases for the network. -.LP +.PP .PP This file is read by the .BR route (8) diff --git a/man5/nsswitch.conf.5 b/man5/nsswitch.conf.5 index 747de3c65a..dfaa4df892 100644 --- a/man5/nsswitch.conf.5 +++ b/man5/nsswitch.conf.5 @@ -33,13 +33,13 @@ the sources from which to obtain name-service information in a range of categories, and in what order. Each category of information is identified by a database name. -.LP +.PP The file is plain ASCII text, with columns separated by spaces or tab characters. The first column specifies the database name. The remaining columns describe the order of sources to query and a limited set of actions that can be performed by lookup result. -.LP +.PP The following databases are understood by the GNU C Library: .TP 12 .B aliases @@ -101,7 +101,7 @@ and related functions. Shadow user passwords, used by .BR getspnam (3) and related functions. -.LP +.PP The GNU C Library ignores databases with unknown names. Some applications use this to implement special handling for their own databases. For example, @@ -109,7 +109,7 @@ databases. For example, consults the .B sudoers database. -.LP +.PP Here is an example .I /etc/nsswitch.conf file: @@ -138,7 +138,7 @@ those services will be queried, in turn, until a result is found. .IP * Optional actions to perform if a particular result is obtained from the preceding service, for example, "[NOTFOUND=return]". -.LP +.PP The service specifications supported on your system depend on the presence of shared libraries, and are therefore extensible. Libraries called @@ -164,20 +164,20 @@ The version number may be 1 for glibc 2.0, or 2 for glibc 2.1 and later. On systems with additional libraries installed, you may have access to further services such as "hesiod", "ldap", "winbind" and "wins". -.LP +.PP An action may also be specified following a service specification. The action modifies the behavior following a result obtained from the preceding data source. Action items take the general form: -.LP +.PP .RS 4 .RI [ STATUS = ACTION ] .br .RI [! STATUS = ACTION ] .RE -.LP +.PP where -.LP +.PP .RS 4 .I STATUS => @@ -197,11 +197,11 @@ where | .B merge .RE -.LP +.PP The ! negates the test, matching all possible results except the one specified. The case of the keywords is not significant. -.LP +.PP The .I STATUS value is matched against the result of the lookup function called by @@ -229,7 +229,7 @@ This could mean a file is locked or a server currently cannot accept more connections. The default action for this condition is "continue". .RE -.LP +.PP The .I ACTION value can be one of: @@ -270,7 +270,7 @@ additionally permits special entries in corresponding files for granting users or members of netgroups access to the system. The following entries are valid in this mode: .RS 4 -.LP +.PP For .B passwd and @@ -300,7 +300,7 @@ Exclude all users in the given Include every user, except previously excluded ones, from the NIS passwd/shadow map. .RE -.LP +.PP For .B group database: @@ -321,7 +321,7 @@ Include every group, except previously excluded ones, from the NIS group map. .RE .RE -.LP +.PP By default, the source is "nis", but this may be overridden by specifying any NSS service except "compat" itself as the source for the pseudo-databases @@ -364,7 +364,7 @@ implements "nis" source. implements "nisplus" source. .PD .RE -.LP +.PP The following files are read when "files" source is specified for respective databases: .RS 4 @@ -416,7 +416,7 @@ Within each process that uses the entire file is read only once. If the file is later changed, the process will continue using the old configuration. -.LP +.PP Traditionally, there was only a single source for service information, often in the form of a single configuration file (e.g., \fI/etc/passwd\fP). diff --git a/man5/protocols.5 b/man5/protocols.5 index 48630ccc17..24110c55eb 100644 --- a/man5/protocols.5 +++ b/man5/protocols.5 @@ -71,7 +71,7 @@ header. .TP .I aliases optional aliases for the protocol. -.LP +.PP This file might be distributed over a network using a network-wide naming service like Yellow Pages/NIS or BIND/Hesiod. .SH FILES diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5 index 118b89ef78..e448a8afa8 100644 --- a/man5/resolv.conf.5 +++ b/man5/resolv.conf.5 @@ -38,12 +38,12 @@ keywords with values that provide various types of resolver information. The configuration file is considered a trusted source of DNS information (e.g., DNSSEC AD-bit information will be returned unmodified from this source). -.LP +.PP If this file does not exist, only the name server on the local machine will be queried; the domain name is determined from the hostname and the domain search path is constructed from the domain name. -.LP +.PP The different configuration options are: .TP \fBnameserver\fP Name server IP address @@ -131,7 +131,7 @@ The syntax is .RS .IP \fBoptions\fP \fIoption\fP \fI...\fP -.LP +.PP where \fIoption\fP is one of the following: .TP \fBdebug\fP @@ -304,22 +304,22 @@ in .IR _res.options . This option forces the use of TCP for DNS resolutions. .RE -.LP +.PP The \fIdomain\fP and \fIsearch\fP keywords are mutually exclusive. If more than one instance of these keywords is present, the last instance wins. -.LP +.PP The \fIsearch\fP keyword of a system's \fIresolv.conf\fP file can be overridden on a per-process basis by setting the environment variable .B LOCALDOMAIN to a space-separated list of search domains. -.LP +.PP The \fIoptions\fP keyword of a system's \fIresolv.conf\fP file can be amended on a per-process basis by setting the environment variable .B RES_OPTIONS to a space-separated list of resolver options as explained above under \fBoptions\fP. -.LP +.PP The keyword and value must appear on a single line, and the keyword (e.g., \fBnameserver\fP) must start the line. The value follows the keyword, separated by white space. diff --git a/man5/slabinfo.5 b/man5/slabinfo.5 index a1510a4c77..6ce69fa5d3 100644 --- a/man5/slabinfo.5 +++ b/man5/slabinfo.5 @@ -37,7 +37,7 @@ The file gives statistics on these caches. The following (edited) output shows an example of the contents of this file: -.LP +.PP .in 0 .nf $ \fBsudo cat /proc/slabinfo\fP @@ -49,7 +49,7 @@ kmalloc-8192 96 96 8192 4 8 : tunables 0 0 0 : slabdata 24 24 0 \&... .fi .in -.LP +.PP The first line of output includes a version number, which allows an application that is reading the file to handle changes in the file format. diff --git a/man5/termcap.5 b/man5/termcap.5 index 0799d69130..d4029b284e 100644 --- a/man5/termcap.5 +++ b/man5/termcap.5 @@ -38,7 +38,7 @@ It is retained only for capability with old programs; new programs should use the .BR terminfo (5) database and associated libraries. -.LP +.PP .I /etc/termcap is an ASCII file (the database master) that lists the capabilities of many different types of terminals. @@ -51,18 +51,18 @@ handled by The termcap database is indexed on the .B TERM environment variable. -.LP +.PP Termcap entries must be defined on a single logical line, with \(aq\\\(aq used to suppress the newline. Fields are separated by \(aq:\(aq. The first field of each entry starts at the left-hand margin, and contains a list of names for the terminal, separated by \(aq|\(aq. -.LP +.PP The first subfield may (in BSD termcap entries from versions 4.3 and earlier) contain a short name consisting of two characters. This short name may consist of capital or small letters. In 4.4BSD, termcap entries this field is omitted. -.LP +.PP The second subfield (first, in the newer 4.4BSD format) contains the name used by the environment variable .BR TERM . @@ -75,15 +75,15 @@ Usual suffixes are w (more than 80 characters wide), am display). The third subfield contains a long and descriptive name for this termcap entry. -.LP +.PP Subsequent fields contain the terminal capabilities; any continued capability lines must be indented one tab from the left margin. -.LP +.PP Although there is no defined order, it is suggested to write first boolean, then numeric, and then string capabilities, each sorted alphabetically without looking at lower or upper spelling. Capabilities of similar functions can be written in one line. -.LP +.PP Example for: .nf .PP @@ -377,15 +377,15 @@ vs Standout cursor wi Set window from line %1 to %2 and column %3 to %4 XF XOFF character if not \fB^S\fP .fi -.LP +.PP There are several ways of defining the control codes for string capabilities: -.LP +.PP Every normal character represents itself, except \(aq^\(aq, \(aq\e\(aq, and \(aq%\(aq. -.LP +.PP A \fB^x\fP means Control-x. Control-A equals 1 decimal. -.LP +.PP \ex means a special code. x can be one of the following characters: .RS @@ -416,7 +416,7 @@ Do ASCII output of this parameter with a field with of 2 Do ASCII output of this parameter with a field with of 3 .IP % Print a \(aq%\(aq -.LP +.PP If you use binary output, then you should avoid the null character (\(aq\\0\(aq) because it terminates the string. You should reset tabulator expansion @@ -424,7 +424,7 @@ if a tabulator can be the binary output of a parameter. .IP Warning: The above metacharacters for parameters may be wrong: they document Minix termcap which may not be compatible with Linux termcap. -.LP +.PP The block graphic characters can be specified by three string capabilities: .IP as start the alternative charset @@ -434,7 +434,7 @@ end the alternative charset pairs of characters. The first character is the name of the block graphic symbol and the second characters is its definition. -.LP +.PP The following names are available: .PP .nf diff --git a/man7/ascii.7 b/man7/ascii.7 index 1a13b92611..7b301b90d4 100644 --- a/man7/ascii.7 +++ b/man7/ascii.7 @@ -41,9 +41,9 @@ ASCII is the American Standard Code for Information Interchange. It is a 7-bit code. Many 8-bit codes (e.g., ISO 8859-1) contain ASCII as their lower half. The international counterpart of ASCII is known as ISO 646-IRV. -.LP +.PP The following table contains the 128 ASCII characters. -.LP +.PP C program \f(CW\(aq\eX\(aq\fP escapes are noted. .if t \{\ .ft CW @@ -157,17 +157,17 @@ F: / ? O _ o DEL An .B ascii manual page appeared in Version 7 of AT&T UNIX. -.LP +.PP On older terminals, the underscore code is displayed as a left arrow, called backarrow, the caret is displayed as an up-arrow and the vertical bar has a hole in the middle. -.LP +.PP Uppercase and lowercase characters differ by just one bit and the ASCII character 2 differs from the double quote by just one bit, too. That made it much easier to encode characters mechanically or with a non-microcontroller-based electronic keyboard and that pairing was found on old teletypes. -.LP +.PP The ASCII standard was published by the United States of America Standards Institute (USASI) in 1968. .\" diff --git a/man7/boot.7 b/man7/boot.7 index 5142c7bde8..cb861932c7 100644 --- a/man7/boot.7 +++ b/man7/boot.7 @@ -16,7 +16,7 @@ .SH NAME boot \- System bootup process based on UNIX System V Release 4 .SH DESCRIPTION -.LP +.PP The \fBbootup process\fR (or "\fBboot sequence\fR") varies in details among systems, but can be roughly divided into phases controlled by the following components: @@ -123,7 +123,7 @@ fundamentally different approach known as .BR systemd (1), for which the bootup process is detailed in its associated .BR bootup (7). -.LP +.PP When .I /sbin/init starts, it reads @@ -154,7 +154,7 @@ Note: The following description applies to an OS based on UNIX System V Release 4. However, a number of widely used systems (Slackware Linux, FreeBSD, OpenBSD) have a somewhat different scheme for boot scripts. -.LP +.PP For each managed service (mail, nfs server, cron, etc.), there is a single startup script located in a specific directory .RI ( /etc/init.d @@ -215,7 +215,7 @@ A boot script in \fI/etc/init.d\fR reads and includes its configuration file (that is, it "\fBsources\fR" its configuration file) and then uses the variable values. .SH FILES -.LP +.PP .IR /etc/init.d/ , .IR /etc/rc[S0\-6].d/ , .I /etc/sysconfig/ diff --git a/man7/bootparam.7 b/man7/bootparam.7 index 319b3d2504..07a39233f6 100644 --- a/man7/bootparam.7 +++ b/man7/bootparam.7 @@ -50,7 +50,7 @@ Most of the boot arguments have the form: name[=value_1][,value_2]...[,value_10] .EE .in -.LP +.PP where 'name' is a unique keyword that is used to identify what part of the kernel the associated values (if any) are to be given to. Note the limit of 10 is real, as the present code handles only 10 comma diff --git a/man7/charsets.7 b/man7/charsets.7 index cfb63db475..2de0ad121f 100644 --- a/man7/charsets.7 +++ b/man7/charsets.7 @@ -22,10 +22,10 @@ This manual page gives an overview on different character set standards and how they were used on Linux before Unicode became ubiquitous. Some of this information is still helpful for people working with legacy systems and documents. -.LP +.PP Standards discussed include such as ASCII, GB 2312, ISO 8859, JIS, KOI8-R, KS, and Unicode. -.LP +.PP The primary emphasis is on character sets that were actually used by locale character sets, not the myriad others that could be found in data from other systems. @@ -35,7 +35,7 @@ ASCII (American Standard Code For Information Interchange) is the original Also known as US-ASCII. It is currently described by the ISO 646:1991 IRV (International Reference Version) standard. -.LP +.PP Various ASCII variants replacing the dollar sign with other currency symbols and replacing punctuation with non-English alphabetic characters to cover German, French, Spanish, and others in 7 bits @@ -43,27 +43,27 @@ emerged. All are deprecated; glibc does not support locales whose character sets are not true supersets of ASCII. -.LP +.PP As Unicode, when using UTF-8, is ASCII-compatible, plain ASCII text still renders properly on modern UTF-8 using systems. .SS ISO 8859 ISO 8859 is a series of 15 8-bit character sets, all of which have ASCII in their low (7-bit) half, invisible control characters in positions 128 to 159, and 96 fixed-width graphics in positions 160-255. -.LP +.PP Of these, the most important is ISO 8859-1 ("Latin Alphabet No .1" / Latin-1). It was widely adopted and supported by different systems, and is gradually being replaced with Unicode. The ISO 8859-1 characters are also the first 256 characters of Unicode. -.LP +.PP Console support for the other 8859 character sets is available under Linux through user-mode utilities (such as .BR setfont (8)) that modify keyboard bindings and the EGA graphics table and employ the "user mapping" font table in the console driver. -.LP +.PP Here are brief descriptions of each set: .TP 8859-1 (Latin-1) @@ -146,7 +146,7 @@ ISO 8859-5. KOI8-U, based on KOI8-R, has better support for Ukrainian. Neither of these sets are ISO-2022 compatible, unlike the ISO 8859 series. -.LP +.PP Console support for KOI8-R is available under Linux through user-mode utilities that modify keyboard bindings and the EGA graphics table, and employ the "user mapping" font table in the console driver. @@ -204,7 +204,7 @@ by the Linux kernel and by .BR xterm (1). Several ISO 2022-based character encodings have been defined, especially for Japanese. -.LP +.PP There are 4 graphic character sets, called G0, G1, G2, and G3, and one of them is the current character set for codes with high bit zero (initially G0), and one of them is the current @@ -214,7 +214,7 @@ essentially a 7-bit character set. It uses codes either 040-0177 (041-0176) or 0240-0377 (0241-0376). G0 always has size 94 and uses codes 041-0176. -.LP +.PP Switching between character sets is done using the shift functions \fB^N\fP (SO or LS1), \fB^O\fP (SI or LS0), ESC n (LS2), ESC o (LS3), ESC N (SS2), ESC O (SS3), ESC ~ (LS1R), ESC } (LS2R), ESC | (LS3R). @@ -225,7 +225,7 @@ for codes with high bit one. The function SS\fIn\fP makes character set G\fIn\fP (\fIn\fP=2 or 3) the current one for the next character only (regardless of the value of its high order bit). -.LP +.PP A 94-character set is designated as G\fIn\fP character set by an escape sequence ESC ( xx (for G0), ESC ) xx (for G1), ESC * xx (for G2), ESC + xx (for G3), where xx is a symbol @@ -237,19 +237,19 @@ instead of number sign), ESC ( B selects ASCII (with dollar instead of currency sign), ESC ( M selects a character set for African languages, ESC ( ! A selects the Cuban character set, and so on. -.LP +.PP A 96-character set is designated as G\fIn\fP character set by an escape sequence ESC \- xx (for G1), ESC . xx (for G2) or ESC / xx (for G3). For example, ESC \- G selects the Hebrew alphabet as G1. -.LP +.PP A multibyte character set is designated as G\fIn\fP character set by an escape sequence ESC $ xx or ESC $ ( xx (for G0), ESC $ ) xx (for G1), ESC $ * xx (for G2), ESC $ + xx (for G3). For example, ESC $ ( C selects the Korean character set for G0. The Japanese character set selected by ESC $ B has a more recent version selected by ESC & @ ESC $ B. -.LP +.PP ISO 4873 stipulates a narrower use of character sets, where G0 is fixed (always ASCII), so that G1, G2 and G3 can be invoked only for codes with the high order bit set. @@ -269,14 +269,14 @@ Since most computers don't include 20.1-bit integers, Unicode is usually encoded as 32-bit integers internally and either a series of 16-bit integers (UTF-16) (needing two 16-bit integers only when encoding certain rare characters) or a series of 8-bit bytes (UTF-8). -.LP +.PP Linux represents Unicode using the 8-bit Unicode Transformation Format (UTF-8). UTF-8 is a variable length encoding of Unicode. It uses 1 byte to code 7 bits, 2 bytes for 11 bits, 3 bytes for 16 bits, 4 bytes for 21 bits, 5 bytes for 26 bits, 6 bytes for 31 bits. -.LP +.PP Let 0,1,x stand for a zero, one, or arbitrary bit. A byte 0xxxxxxx stands for the Unicode 00000000 0xxxxxxx which codes the same symbol @@ -284,7 +284,7 @@ as the ASCII 0xxxxxxx. Thus, ASCII goes unchanged into UTF-8, and people using only ASCII do not notice any change: not in code, and not in file size. -.LP +.PP A byte 110xxxxx is the start of a 2-byte code, and 110xxxxx 10yyyyyy is assembled into 00000xxx xxyyyyyy. A byte 1110xxxx is the start @@ -292,7 +292,7 @@ of a 3-byte code, and 1110xxxx 10yyyyyy 10zzzzzz is assembled into xxxxyyyy yyzzzzzz. (When UTF-8 is used to code the 31-bit ISO 10646 then this progression continues up to 6-byte codes.) -.LP +.PP For most texts in ISO 8859 character sets, this means that the characters outside of ASCII are now coded with two bytes. This tends @@ -306,19 +306,19 @@ While there are algorithmic conversions from some character sets (especially ISO 8859-1) to Unicode, general conversion requires carrying around conversion tables, which can be quite large for 16-bit codes. -.LP +.PP Note that UTF-8 is self-synchronizing: 10xxxxxx is a tail, any other byte is the head of a code. Note that the only way ASCII bytes occur in a UTF-8 stream, is as themselves. In particular, there are no embedded NULs (\(aq\\0\(aq) or \(aq/\(aqs that form part of some larger code. -.LP +.PP Since ASCII, and, in particular, NUL and \(aq/\(aq, are unchanged, the kernel does not notice that UTF-8 is being used. It does not care at all what the bytes it is handling stand for. -.LP +.PP Rendering of Unicode data streams is typically handled through "subfont" tables which map a subset of Unicode to glyphs. Internally diff --git a/man7/icmp.7 b/man7/icmp.7 index e1c2a4e19a..c6f5bfa217 100644 --- a/man7/icmp.7 +++ b/man7/icmp.7 @@ -32,7 +32,7 @@ The types of ICMP packets passed to the socket can be filtered using the socket option. ICMP packets are always processed by the kernel too, even when passed to a user socket. -.LP +.PP Linux limits the rate of ICMP error packets to each destination. .B ICMP_REDIRECT and diff --git a/man7/inode.7 b/man7/inode.7 index 9e176b1610..3c3614ca29 100644 --- a/man7/inode.7 +++ b/man7/inode.7 @@ -406,7 +406,7 @@ then define with the value 500 or greater (before including .I any header files). -.LP +.PP POSIX.1-1990 did not describe the .BR S_IFMT , .BR S_IFSOCK , @@ -432,7 +432,7 @@ and macros were not in POSIX.1-1996, but both are present in POSIX.1-2001; the former is from SVID 4, the latter from SUSv2. -.LP +.PP UNIX\ V7 (and later systems) had .BR S_IREAD , .BR S_IWRITE , diff --git a/man7/man.7 b/man7/man.7 index a76c8803b9..1d9e4595e4 100644 --- a/man7/man.7 +++ b/man7/man.7 @@ -38,11 +38,11 @@ man \- macros to format man pages .B groff \-Tascii \-man .I file \&... -.LP +.PP .B groff \-Tps \-man .I file \&... -.LP +.PP .B man .RI [ section ] .I title @@ -163,7 +163,7 @@ Small alternating with bold .TP .B \&.SM Small (useful for acronyms) -.LP +.PP Traditionally, each command can have up to six arguments, but the GNU implementation removes this limitation (you might still want to limit yourself to 6 arguments for portability's sake). @@ -495,7 +495,7 @@ to make the formatting consistent for a given media, and to automatically insert cross-references. By sticking to the safe subset described above, it should be easier to automate transitioning to a different reference page format in the future. -.LP +.PP The Sun macro .B TX is not implemented. diff --git a/man7/netdevice.7 b/man7/netdevice.7 index b92344a08b..d1097effe6 100644 --- a/man7/netdevice.7 +++ b/man7/netdevice.7 @@ -346,12 +346,12 @@ and the other ioctls that accept or return only socket addresses, are IP-specific and belong in .BR ip (7). -.LP +.PP The names of interfaces with no addresses or that don't have the .B IFF_RUNNING flag set can be found via .IR /proc/net/dev . -.LP +.PP Local IPv6 IP addresses can be found via .I /proc/net or via diff --git a/man7/posixoptions.7 b/man7/posixoptions.7 index 8ca0ce7c30..74bc55c47d 100644 --- a/man7/posixoptions.7 +++ b/man7/posixoptions.7 @@ -38,7 +38,7 @@ From shell scripts one can use .BR getconf (1). For more detail, see .BR sysconf (3). -.LP +.PP We give the name of the POSIX abbreviation, the option, the name of the .BR sysconf (3) parameter used to inquire about the option, and possibly diff --git a/man8/ld.so.8 b/man8/ld.so.8 index 9a7f739231..734f22aa58 100644 --- a/man8/ld.so.8 +++ b/man8/ld.so.8 @@ -23,14 +23,14 @@ and .B ld\-linux.so* find and load the shared objects (shared libraries) needed by a program, prepare the program to run, and then run it. -.LP +.PP Linux binaries require dynamic linking (linking at run time) unless the .B \-static option was given to .BR ld (1) during compilation. -.LP +.PP The program .B ld.so handles a.out binaries, a format used long ago; @@ -44,7 +44,7 @@ support files and programs .BR ldconfig (8), and .IR /etc/ld.so.conf . -.LP +.PP When resolving shared object dependencies, the dynamic linker first inspects each dependency string to see if it contains a slash (this can occur if @@ -52,7 +52,7 @@ a shared object pathname containing slashes was specified at link time). If a slash is found, then the dependency string is interpreted as a (relative or absolute) pathname, and the shared object is loaded using that pathname. -.LP +.PP If a shared object dependency does not contain a slash, then it is searched for in the following order: .IP o 3 @@ -344,7 +344,7 @@ If set (to any value), causes the program to list its dynamic dependencies, as if run by .BR ldd (1), instead of running normally. -.LP +.PP Then there are lots of more or less obscure variables, many obsolete or only for internal use. .TP |