Changes, access.2, clone.2, aio_init.3, atexit.3, makecontext.3, makedev.3, pthread_attr_setdetachstate.3, pthread_exit.3: Remove redundant section number in page references

Remove section number in function references that are for
functions documented on this page.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2010-11-01 06:59:37 +01:00
parent 54c42ab095
commit 27d47e71ef
9 changed files with 18 additions and 12 deletions

View File

@ -120,6 +120,12 @@ Various pages
Michael Kerrisk
SEE ALSO: Place entries in correct order
Various pages
Michael Kerrisk
Remove redundant section number in page references
Remove section number in function references that are for
functions documented on this page.
armscii-8.7
iso_8859-3.7
iso_8859-4.7

View File

@ -163,7 +163,7 @@ a safer alternative would be to temporarily switch the process's
effective user ID to the real ID and then call
.BR open (2).)
.PP
.BR access (2)
.BR access ()
always dereferences symbolic links.
If you need to check the permissions on a symbolic link, use
.BR faccessat(2)

View File

@ -390,7 +390,7 @@ somewhat like a standalone system, and calls to
.BR fork (2),
.BR vfork (2),
or
.BR clone (2)
.BR clone ()
will produce processes with PIDs that are unique within the namespace.
The first process created in a new namespace

View File

@ -35,7 +35,7 @@ aio_init \- POSIX asynchronous I/O initialization
Link with \fI\-lrt\fP.
.SH DESCRIPTION
The GNU-specific
.BR aio_init (3)
.BR aio_init ()
function allows the caller to provide tuning hints to the
glibc POSIX AIO implementation.
Use of this function is optional, but to be effective,

View File

@ -90,7 +90,7 @@ POSIX.1-2001 says that the result of calling
more than once (i.e., calling
.BR exit (3)
within a function registered using
.BR atexit (3))
.BR atexit ())
is undefined.
On some systems (but not Linux), this can result in an infinite recursion;
.\" This can happen on OpenBSD 4.2 for example, and is documented
@ -100,7 +100,7 @@ On some systems (but not Linux), this can result in an infinite recursion;
portable programs should not invoke
.BR exit (3)
inside a function registered using
.BR atexit (3).
.BR atexit ().
The
.BR atexit ()

View File

@ -1,4 +1,4 @@
.\" Copyright (C) 2001 Andries Brouwer (aeb@cwi.nl)
\" Copyright (C) 2001 Andries Brouwer (aeb@cwi.nl)
.\" and Copyright (C) 2006 Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" Permission is granted to make and distribute verbatim copies of this
@ -129,7 +129,7 @@ is undefined according to the standards,
and won't work on architectures where pointers are larger than
.IR int s.
Nevertheless, starting with version 2.8, glibc makes some changes to
.BR makecontext (3),
.BR makecontext (),
to permit this on some 64-bit architectures (e.g., x86-64).
.SH EXAMPLE
.PP

View File

@ -71,10 +71,10 @@ but are present on many other systems.
These interfaces are defined as macros.
Since glibc 2.3.3,
they have been aliases for three GNU-specific functions:
.BR gnu_dev_makedev (3),
.BR gnu_dev_major (3),
.BR gnu_dev_makedev (),
.BR gnu_dev_major (),
and
.BR gnu_dev_minor (3).
.BR gnu_dev_minor ().
The latter names are exported, but the traditional names are more portable.
.SH "SEE ALSO"
.BR mknod (2),

View File

@ -75,7 +75,7 @@ in the buffer pointed to by
On success, these functions return 0;
on error, they return a nonzero error number.
.SH ERRORS
.BR pthread_attr_setdetachstate (3)
.BR pthread_attr_setdetachstate ()
can fail with the following error:
.TP
.B EINVAL

View File

@ -95,7 +95,7 @@ there are limitations in the kernel implementation logic for
on a stopped thread group with a dead thread group leader.
This can manifest in problems such as a locked terminal if a stop signal is
sent to a foreground process whose thread group leader has already called
.BR pthread_exit (3).
.BR pthread_exit ().
.\" FIXME . review a later kernel to see if this gets fixed
.\" http://thread.gmane.org/gmane.linux.kernel/611611
.\" http://marc.info/?l=linux-kernel&m=122525468300823&w=2