mirror of https://github.com/mkerrisk/man-pages
intro.1, time.1, accept.2, bind.2, connect.2, execve.2, flock.2, getdents.2, getpriority.2, getuid.2, intro.2, ioctl.2, mincore.2, mknod.2, personality.2, ptrace.2, read.2, recv.2, select_tut.2, send.2, sendfile.2, shmctl.2, sigaction.2, signal.2, stat.2, times.2, truncate.2, umask.2, wait.2, MB_CUR_MAX.3, MB_LEN_MAX.3, argz_add.3, btowc.3, clearenv.3, clock.3, cmsg.3, end.3, endian.3, errno.3, exit.3, fgetwc.3, fgetws.3, fopen.3, fputwc.3, fputws.3, fseek.3, fwide.3, getfsent.3, getgrnam.3, gethostid.3, getipnodebyname.3, getmntent.3, getpwnam.3, getwchar.3, grantpt.3, iconv.3, iconv_close.3, iconv_open.3, insque.3, intro.3, iswalnum.3, iswalpha.3, iswblank.3, iswcntrl.3, iswctype.3, iswdigit.3, iswgraph.3, iswlower.3, iswprint.3, iswpunct.3, iswspace.3, iswupper.3, iswxdigit.3, malloc.3, mblen.3, mbrlen.3, mbrtowc.3, mbsinit.3, mbsnrtowcs.3, mbsrtowcs.3, mbstowcs.3, mbtowc.3, mkstemp.3, mktemp.3, nl_langinfo.3, openpty.3, posix_openpt.3, printf.3, ptsname.3, putwchar.3, qecvt.3, rcmd.3, readdir.3, rexec.3, rpc.3, setnetgrent.3, shm_open.3, sigpause.3, stdin.3, stpcpy.3, strftime.3, strptime.3, syslog.3, towctrans.3, towlower.3, towupper.3, ttyslot.3, ungetwc.3, unlocked_stdio.3, wcpcpy.3, wcpncpy.3, wcrtomb.3, wcscasecmp.3, wcscat.3, wcschr.3, wcscmp.3, wcscpy.3, wcscspn.3, wcsdup.3, wcslen.3, wcsncasecmp.3, wcsncat.3, wcsncmp.3, wcsncpy.3, wcsnlen.3, wcsnrtombs.3, wcspbrk.3, wcsrchr.3, wcsrtombs.3, wcsspn.3, wcsstr.3, wcstok.3, wcstombs.3, wcswidth.3, wctob.3, wctomb.3, wctrans.3, wctype.3, wcwidth.3, wmemchr.3, wmemcmp.3, wmemcpy.3, wmemmove.3, wmemset.3, wprintf.3, console_ioctl.4, pts.4, elf.5, filesystems.5, hosts.5, proc.5, ttytype.5, boot.7, capabilities.7, credentials.7, epoll.7, glob.7, koi8-r.7, path_resolution.7, pty.7, signal.7, suffixes.7, time.7, unicode.7, unix.7, uri.7, utf-8.7: global fix: s/Unix/UNIX/
The man pages were rather inconsistent in the use of "Unix" versus "UNIX". Let's go with the trademark usage. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
1f409d5d0b
commit
008f1ecc43
10
man1/intro.1
10
man1/intro.1
|
@ -44,14 +44,14 @@ A nonzero exit status can be in the range 1 to 255, and some commands
|
|||
use different nonzero status values to indicate the reason why the
|
||||
command failed.
|
||||
.SH NOTES
|
||||
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).
|
||||
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
|
||||
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.
|
||||
The traditional Unix environment
|
||||
The traditional UNIX environment
|
||||
is a CLI (command line interface), where you type commands to
|
||||
tell the computer what to do.
|
||||
That is faster and more powerful,
|
||||
|
@ -247,7 +247,7 @@ The command
|
|||
.I df
|
||||
will tell you how much of your disk is still free.
|
||||
.SS "Processes"
|
||||
On a Unix system many user and system processes run simultaneously.
|
||||
On a UNIX system many user and system processes run simultaneously.
|
||||
The one you are talking to runs in the
|
||||
.IR foreground ,
|
||||
the others in the
|
||||
|
|
|
@ -247,7 +247,7 @@ Print version information on standard output, then exit successfully.
|
|||
.B "\-\-"
|
||||
Terminate option list.
|
||||
.SH BUGS
|
||||
Not all resources are measured by all versions of Unix,
|
||||
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.
|
||||
|
|
|
@ -354,7 +354,7 @@ and on many other systems like 4.x BSD, SunOS 4, SGI); a POSIX.1g draft
|
|||
standard wanted to change it into a \fIsize_t *\fP, and that is what it is
|
||||
for SunOS 5.
|
||||
Later POSIX drafts have \fIsocklen_t *\fP,
|
||||
and so do the Single Unix Specification and glibc2.
|
||||
and so do the Single UNIX Specification and glibc2.
|
||||
Quoting Linus Torvalds:
|
||||
|
||||
.\" .I fails: only italicizes a single line
|
||||
|
|
|
@ -174,7 +174,7 @@ The socket is already bound to an address.
|
|||
.I sockfd
|
||||
is a descriptor for a file, not a socket.
|
||||
.PP
|
||||
The following errors are specific to Unix domain
|
||||
The following errors are specific to UNIX domain
|
||||
.RB ( AF_UNIX )
|
||||
sockets:
|
||||
.TP
|
||||
|
@ -228,7 +228,7 @@ first appeared in 4.2BSD).
|
|||
.\" .B EIO
|
||||
.\" and
|
||||
.\" .B EISDIR
|
||||
.\" Unix-domain error conditions.
|
||||
.\" UNIX-domain error conditions.
|
||||
.SH NOTES
|
||||
POSIX.1-2001 does not require the inclusion of
|
||||
.IR <sys/types.h> ,
|
||||
|
@ -255,7 +255,7 @@ An example of the use of
|
|||
with Internet domain sockets can be found in
|
||||
.BR getaddrinfo (3).
|
||||
|
||||
The following example shows how to bind a stream socket in the Unix
|
||||
The following example shows how to bind a stream socket in the UNIX
|
||||
.RB ( AF_UNIX )
|
||||
domain, and accept connections:
|
||||
.\" listen.7 refers to this example.
|
||||
|
|
|
@ -132,7 +132,7 @@ The following are general socket errors only.
|
|||
There may be other domain-specific error codes.
|
||||
.TP
|
||||
.B EACCES
|
||||
For Unix domain sockets, which are identified by pathname:
|
||||
For UNIX domain sockets, which are identified by pathname:
|
||||
Write permission is denied on the socket file,
|
||||
or search permission is denied for one of the directories
|
||||
in the path prefix.
|
||||
|
|
|
@ -280,7 +280,7 @@ For portable use,
|
|||
should either be absent, or be specified as a single word (i.e., it
|
||||
should not contain white space); see NOTES below.
|
||||
.SS "Limits on size of arguments and environment"
|
||||
Most Unix implementations impose some limit on the total size
|
||||
Most UNIX implementations impose some limit on the total size
|
||||
of the command-line argument
|
||||
.RI ( argv )
|
||||
and environment
|
||||
|
@ -484,7 +484,7 @@ which has the same effect as specifying this argument
|
|||
as a pointer to a list containing a single NULL pointer.
|
||||
.B "Do not take advantage of this misfeature!"
|
||||
It is nonstandard and nonportable:
|
||||
on most other Unix systems doing this will result in an error
|
||||
on most other UNIX systems doing this will result in an error
|
||||
.RB ( EFAULT ).
|
||||
.\" e.g., EFAULT on Solaris 8 and FreeBSD 6.1; but
|
||||
.\" HP-UX 11 is like Linux -- mtk, Apr 2007
|
||||
|
@ -512,7 +512,7 @@ command-line arguments and environment variables has changed.
|
|||
.\" that could be exploited for denial of service by a suitably crafted
|
||||
.\" ELF binary. There are no known problems with 2.0.34 or 2.2.15.
|
||||
.SS Historical
|
||||
With Unix V6 the argument list of an
|
||||
With UNIX V6 the argument list of an
|
||||
.BR exec ()
|
||||
call was ended by 0,
|
||||
while the argument list of
|
||||
|
@ -521,7 +521,7 @@ was ended by \-1.
|
|||
Thus, this argument list was not directly usable in a further
|
||||
.BR exec ()
|
||||
call.
|
||||
Since Unix V7 both are NULL.
|
||||
Since UNIX V7 both are NULL.
|
||||
.SH EXAMPLE
|
||||
The following program is designed to be execed by the second program below.
|
||||
It just echoes its command-line one per line.
|
||||
|
|
|
@ -143,7 +143,7 @@ A version of
|
|||
.BR flock (),
|
||||
possibly implemented in terms of
|
||||
.BR fcntl (2),
|
||||
appears on most Unix systems.
|
||||
appears on most UNIX systems.
|
||||
.SH NOTES
|
||||
.BR flock ()
|
||||
does not lock files over NFS.
|
||||
|
|
|
@ -110,7 +110,7 @@ This is a symbolic link.
|
|||
This is a regular file.
|
||||
.TP
|
||||
.B DT_SOCK
|
||||
This is a Unix domain socket.
|
||||
This is a UNIX domain socket.
|
||||
.TP
|
||||
.B DT_UNKNOWN
|
||||
The file type is unknown.
|
||||
|
|
|
@ -166,7 +166,7 @@ The nice value is preserved across
|
|||
.BR execve (2).
|
||||
|
||||
The degree to which their relative nice value affects the scheduling of
|
||||
processes varies across Unix systems, and,
|
||||
processes varies across UNIX systems, and,
|
||||
on Linux, across kernel versions.
|
||||
Starting with kernel 2.6.23, Linux adopted an algorithm that causes
|
||||
relative differences in nice values to have a much stronger effect.
|
||||
|
|
|
@ -46,11 +46,11 @@ These functions are always successful.
|
|||
POSIX.1-2001, 4.3BSD.
|
||||
.SH NOTES
|
||||
.SS History
|
||||
In Unix V6 the
|
||||
In UNIX V6 the
|
||||
.BR getuid ()
|
||||
call returned
|
||||
.IR "(euid << 8) + uid" .
|
||||
Unix V7 introduced separate calls
|
||||
UNIX V7 introduced separate calls
|
||||
.BR getuid ()
|
||||
and
|
||||
.BR geteuid ().
|
||||
|
|
|
@ -66,7 +66,7 @@ In such cases, the required macro is described in the man page.
|
|||
For further information on feature test macros, see
|
||||
.BR feature_test_macros (7).
|
||||
.SH "CONFORMING TO"
|
||||
Certain terms and abbreviations are used to indicate Unix variants
|
||||
Certain terms and abbreviations are used to indicate UNIX variants
|
||||
and standards to which calls in this section conform.
|
||||
See
|
||||
.BR standards (7).
|
||||
|
|
|
@ -117,7 +117,7 @@ No single standard.
|
|||
Arguments, returns, and semantics of
|
||||
.BR ioctl ()
|
||||
vary according to the device driver in question (the call is used as a
|
||||
catch-all for operations that don't cleanly fit the Unix stream I/O
|
||||
catch-all for operations that don't cleanly fit the UNIX stream I/O
|
||||
model).
|
||||
See
|
||||
.BR ioctl_list (2)
|
||||
|
@ -126,7 +126,7 @@ for a list of many of the known
|
|||
calls.
|
||||
The
|
||||
.BR ioctl ()
|
||||
function call appeared in Version 7 AT&T Unix.
|
||||
function call appeared in Version 7 AT&T UNIX.
|
||||
.SH NOTES
|
||||
In order to use this call, one needs an open file descriptor.
|
||||
Often the
|
||||
|
|
|
@ -134,7 +134,7 @@ Available since Linux 2.3.99pre1 and glibc 2.2.
|
|||
.SH "CONFORMING TO"
|
||||
.BR mincore ()
|
||||
is not specified in POSIX.1-2001,
|
||||
and it is not available on all Unix implementations.
|
||||
and it is not available on all UNIX implementations.
|
||||
.\" It is on at least NetBSD, FreeBSD, OpenBSD, Solaris 8,
|
||||
.\" AIX 5.1, SunOS 4.1
|
||||
.\" .SH HISTORY
|
||||
|
|
|
@ -67,7 +67,7 @@ or
|
|||
.B S_IFSOCK
|
||||
.\" (S_IFSOCK since Linux 1.2.4)
|
||||
to specify a regular file (which will be created empty), character
|
||||
special file, block special file, FIFO (named pipe), or Unix domain socket,
|
||||
special file, block special file, FIFO (named pipe), or UNIX domain socket,
|
||||
respectively.
|
||||
(Zero file type is equivalent to type
|
||||
.BR S_IFREG .)
|
||||
|
@ -155,11 +155,11 @@ is not, in fact, a directory.
|
|||
.B EPERM
|
||||
.I mode
|
||||
requested creation of something other than a regular file,
|
||||
FIFO (named pipe), or Unix domain socket, and the caller
|
||||
FIFO (named pipe), or UNIX domain socket, and the caller
|
||||
is not privileged (Linux: does not have the
|
||||
.B CAP_MKNOD
|
||||
capability);
|
||||
.\" For Unix domain sockets and regular files, EPERM is only returned in
|
||||
.\" For UNIX domain sockets and regular files, EPERM is only returned in
|
||||
.\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can
|
||||
.\" use mknod() to make these files.
|
||||
also returned if the file system containing
|
||||
|
@ -196,7 +196,7 @@ a function especially defined for this purpose.
|
|||
Under Linux, this call cannot be used to create directories.
|
||||
One should make directories with
|
||||
.BR mkdir (2).
|
||||
.\" and one should make Unix domain sockets with socket(2) and bind(2).
|
||||
.\" and one should make UNIX domain sockets with socket(2) and bind(2).
|
||||
|
||||
There are many infelicities in the protocol underlying NFS.
|
||||
Some of these affect
|
||||
|
|
|
@ -41,7 +41,7 @@ Among other things, execution domains tell Linux how to map
|
|||
signal numbers into signal actions.
|
||||
The execution domain system allows
|
||||
Linux to provide limited support for binaries compiled under other
|
||||
Unix-like operating systems.
|
||||
UNIX-like operating systems.
|
||||
|
||||
This function will return the current
|
||||
.BR personality ()
|
||||
|
|
|
@ -501,7 +501,7 @@ after receiving one of these messages.
|
|||
This page documents the way the
|
||||
.BR ptrace ()
|
||||
call works currently in Linux.
|
||||
Its behavior differs noticeably on other flavors of Unix.
|
||||
Its behavior differs noticeably on other flavors of UNIX.
|
||||
In any case, use of
|
||||
.BR ptrace ()
|
||||
is highly OS- and architecture-specific.
|
||||
|
|
|
@ -163,7 +163,7 @@ leave st_atime (last file access time)
|
|||
updates to the server and client side reads satisfied from the
|
||||
client's cache will not cause st_atime updates on the server as there are no
|
||||
server side reads.
|
||||
Unix semantics can be obtained by disabling client
|
||||
UNIX semantics can be obtained by disabling client
|
||||
side attribute caching, but in most situations this will substantially
|
||||
increase server load and decrease performance.
|
||||
.PP
|
||||
|
|
12
man2/recv.2
12
man2/recv.2
|
@ -71,11 +71,11 @@ When
|
|||
is NULL, nothing is filled in; in this case,
|
||||
.I addrlen
|
||||
is not used, and should also be NULL.
|
||||
.\" (Note: for datagram sockets in both the Unix and Internet domains,
|
||||
.\" (Note: for datagram sockets in both the UNIX and Internet domains,
|
||||
.\" .I src_addr
|
||||
.\" is filled in.
|
||||
.\" .I src_addr
|
||||
.\" is also filled in for stream sockets in the Unix domain, but is not
|
||||
.\" is also filled in for stream sockets in the UNIX domain, but is not
|
||||
.\" filled in for stream sockets in the Internet domain.)
|
||||
.\" [The above notes on AF_UNIX and AF_INET sockets apply as at
|
||||
.\" Kernel 2.4.18. (MTK, 22 Jul 02)]
|
||||
|
@ -135,7 +135,7 @@ one or more of the following values:
|
|||
.TP
|
||||
.BR MSG_CMSG_CLOEXEC " (" recvmsg "() only; since Linux 2.6.23)"
|
||||
Set the close-on-exec flag for the file descriptor received
|
||||
via a Unix domain file descriptor using the
|
||||
via a UNIX domain file descriptor using the
|
||||
.B SCM_RIGHTS
|
||||
operation (described in
|
||||
.BR unix (7)).
|
||||
|
@ -269,7 +269,7 @@ Internet datagram (since Linux 2.4.27/2.6.8),
|
|||
and netlink (since Linux 2.6.22) sockets:
|
||||
return the real length of the packet or datagram,
|
||||
even when it was longer than the passed buffer.
|
||||
Not implemented for Unix domain
|
||||
Not implemented for UNIX domain
|
||||
.RB ( unix (7))
|
||||
sockets.
|
||||
|
||||
|
@ -356,7 +356,7 @@ Ancillary data should only be accessed by the macros defined in
|
|||
.BR cmsg (3).
|
||||
.PP
|
||||
As an example, Linux uses this ancillary data mechanism to pass extended
|
||||
errors, IP options, or file descriptors over Unix sockets.
|
||||
errors, IP options, or file descriptors over UNIX sockets.
|
||||
.PP
|
||||
The
|
||||
.I msg_flags
|
||||
|
@ -452,7 +452,7 @@ and
|
|||
flags.
|
||||
.SH NOTES
|
||||
The prototypes given above follow glibc2.
|
||||
The Single Unix Specification agrees, except that it has return values
|
||||
The Single UNIX Specification agrees, except that it has return values
|
||||
of type \fIssize_t\fP (while 4.x BSD and libc4 and libc5 all have \fIint\fP).
|
||||
The
|
||||
.I flags
|
||||
|
|
|
@ -317,7 +317,7 @@ The point of
|
|||
is that it watches
|
||||
multiple descriptors at the same time and properly puts the process to
|
||||
sleep if there is no activity.
|
||||
Unix programmers often find
|
||||
UNIX programmers often find
|
||||
themselves in a position where they have to handle I/O from more than one
|
||||
file descriptor where the data flow may be intermittent.
|
||||
If you were to merely create a sequence of
|
||||
|
@ -479,7 +479,7 @@ follows:
|
|||
select(0, NULL, NULL, NULL, &tv);
|
||||
.fi
|
||||
.PP
|
||||
This is only guaranteed to work on Unix systems, however.
|
||||
This is only guaranteed to work on UNIX systems, however.
|
||||
.SH RETURN VALUE
|
||||
On success,
|
||||
.BR select ()
|
||||
|
|
|
@ -282,7 +282,7 @@ may be generated and returned from the underlying protocol modules;
|
|||
see their respective manual pages.
|
||||
.TP
|
||||
.B EACCES
|
||||
(For Unix domain sockets, which are identified by pathname)
|
||||
(For UNIX domain sockets, which are identified by pathname)
|
||||
Write permission is denied on the destination socket file,
|
||||
or search permission is denied for one of the directories
|
||||
the path prefix.
|
||||
|
@ -373,7 +373,7 @@ The
|
|||
.B MSG_CONFIRM
|
||||
flag is a Linux extension.
|
||||
.SH NOTES
|
||||
The prototypes given above follow the Single Unix Specification,
|
||||
The prototypes given above follow the Single UNIX Specification,
|
||||
as glibc2 also does; the
|
||||
.I flags
|
||||
argument was \fIint\fP in 4.x BSD, but \fIunsigned int\fP in libc4 and libc5;
|
||||
|
|
|
@ -148,7 +148,7 @@ is present since glibc 2.1.
|
|||
.SH "CONFORMING TO"
|
||||
Not specified in POSIX.1-2001, or other standards.
|
||||
|
||||
Other Unix systems implement
|
||||
Other UNIX systems implement
|
||||
.BR sendfile ()
|
||||
with different semantics and prototypes.
|
||||
It should not be used in portable programs.
|
||||
|
|
|
@ -385,7 +385,7 @@ Linux permits a process to attach
|
|||
a shared memory segment that has already been marked for deletion
|
||||
using
|
||||
.IR shmctl(IPC_RMID) .
|
||||
This feature is not available on other Unix implementations;
|
||||
This feature is not available on other UNIX implementations;
|
||||
portable applications should avoid relying on it.
|
||||
|
||||
Various fields in a \fIstruct shmid_ds\fP were typed as
|
||||
|
|
|
@ -716,7 +716,7 @@ and
|
|||
Use of these latter values in
|
||||
.I sa_flags
|
||||
may be less portable in applications intended for older
|
||||
Unix implementations.
|
||||
UNIX implementations.
|
||||
.PP
|
||||
The
|
||||
.B SA_RESETHAND
|
||||
|
|
|
@ -43,7 +43,7 @@ signal \- ANSI C signal handling
|
|||
.SH DESCRIPTION
|
||||
The behavior of
|
||||
.BR signal ()
|
||||
varies across Unix versions,
|
||||
varies across UNIX versions,
|
||||
and has also varied historically across different versions of Linux.
|
||||
\fBAvoid its use\fP: use
|
||||
.BR sigaction (2)
|
||||
|
@ -178,7 +178,7 @@ which provides explicit control of the semantics when a
|
|||
signal handler is invoked; use that interface instead of
|
||||
.BR signal ().
|
||||
|
||||
In the original Unix systems, when a handler that was established using
|
||||
In the original UNIX systems, when a handler that was established using
|
||||
.BR signal ()
|
||||
was invoked by the delivery of a signal,
|
||||
the disposition of the signal would be reset to
|
||||
|
|
|
@ -404,7 +404,7 @@ macros are not in
|
|||
POSIX.1-1996, but both are present in POSIX.1-2001;
|
||||
the former is from SVID 4, the latter from SUSv2.
|
||||
.LP
|
||||
Unix V7 (and later systems) had
|
||||
UNIX V7 (and later systems) had
|
||||
.BR S_IREAD ,
|
||||
.BR S_IWRITE ,
|
||||
.BR S_IEXEC ,
|
||||
|
|
|
@ -147,7 +147,7 @@ argument can be specified as NULL, with the result that
|
|||
.BR times ()
|
||||
just returns a function result.
|
||||
However, POSIX does not specify this behavior, and most
|
||||
other Unix implementations require a non-NULL value for
|
||||
other UNIX implementations require a non-NULL value for
|
||||
.IR buf .
|
||||
.LP
|
||||
Note that
|
||||
|
@ -165,7 +165,7 @@ is measured has varied across kernel versions.
|
|||
On Linux 2.4 and earlier this point is the moment the system was booted.
|
||||
Since Linux 2.6, this point is \fI(2^32/HZ) \- 300\fP
|
||||
(i.e., about 429 million) seconds before system boot time.
|
||||
This variability across kernel versions (and across Unix implementations),
|
||||
This variability across kernel versions (and across UNIX implementations),
|
||||
combined with the fact that the returned value may overflow the range of
|
||||
.IR clock_t ,
|
||||
means that a portable application would be wise to avoid using this value.
|
||||
|
|
|
@ -218,7 +218,7 @@ exceeds the file length
|
|||
.BR truncate ()
|
||||
is not specified at all in such an environment):
|
||||
either returning an error, or extending the file.
|
||||
Like most Unix implementations, Linux follows the XSI requirement
|
||||
Like most UNIX implementations, Linux follows the XSI requirement
|
||||
when dealing with native file systems.
|
||||
However, some nonnative file systems do not permit
|
||||
.BR truncate ()
|
||||
|
|
|
@ -105,7 +105,7 @@ The umask setting also affects the permissions assigned to POSIX IPC objects
|
|||
.BR shm_open (3)),
|
||||
FIFOs
|
||||
.RB ( mkfifo (3)),
|
||||
and Unix domain sockets
|
||||
and UNIX domain sockets
|
||||
.RB ( unix (7))
|
||||
created by the process.
|
||||
The umask does not affect the permissions assigned
|
||||
|
|
|
@ -217,7 +217,7 @@ This macro should only be employed if
|
|||
.B WIFSIGNALED
|
||||
returned true.
|
||||
This macro is not specified in POSIX.1-2001 and is not available on
|
||||
some Unix implementations (e.g., AIX, SunOS).
|
||||
some UNIX implementations (e.g., AIX, SunOS).
|
||||
Only use this enclosed in #ifdef WCOREDUMP ... #endif.
|
||||
.TP
|
||||
.BI WIFSTOPPED( status )
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\"
|
||||
.\" Modified, aeb, 990824
|
||||
.\"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\"
|
||||
.\" Modified, aeb, 990824
|
||||
.\"
|
||||
|
|
|
@ -82,7 +82,7 @@ is similar, but splits the string
|
|||
.I str
|
||||
into substrings separated by the delimiter
|
||||
.IR delim .
|
||||
For example, one might use this on a Unix search path with
|
||||
For example, one might use this on a UNIX search path with
|
||||
delimiter \(aq:\(aq.
|
||||
.LP
|
||||
.BR argz_append ()
|
||||
|
@ -105,7 +105,7 @@ the number of null bytes (\(aq\\0\(aq), in
|
|||
.RI ( argz ,\ argz_len ).
|
||||
.LP
|
||||
.BR argz_create ()
|
||||
converts a Unix-style argument vector
|
||||
converts a UNIX-style argument vector
|
||||
.IR argv ,
|
||||
terminated by
|
||||
.IR "(char *) 0" ,
|
||||
|
@ -138,7 +138,7 @@ It takes the argz vector
|
|||
and fills the array starting at
|
||||
.I argv
|
||||
with pointers to the substrings, and a final NULL,
|
||||
making a Unix-style argv vector.
|
||||
making a UNIX-style argv vector.
|
||||
The array
|
||||
.I argv
|
||||
must have room for
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH BTOWC 3 2009-02-04 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -50,13 +50,13 @@ The
|
|||
.BR clearenv ()
|
||||
function returns zero on success, and a nonzero
|
||||
value on failure.
|
||||
.\" Most versions of Unix return -1 on error, or do not even have errors.
|
||||
.\" Most versions of UNIX return -1 on error, or do not even have errors.
|
||||
.\" Glibc info and the Watcom C library document "a nonzero value".
|
||||
.SH VERSIONS
|
||||
Not in libc4, libc5.
|
||||
In glibc since glibc 2.0.
|
||||
.SH "CONFORMING TO"
|
||||
Various Unix variants (DG/UX, HP-UX, QNX, ...).
|
||||
Various UNIX variants (DG/UX, HP-UX, QNX, ...).
|
||||
POSIX.9 (bindings for FORTRAN77).
|
||||
POSIX.1-1996 did not accept
|
||||
.BR clearenv ()
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
.\" License.
|
||||
.\" Modified Sat Jul 24 21:27:01 1993 by Rik Faith (faith@cs.unc.edu)
|
||||
.\" Modified 14 Jun 2002, Michael Kerrisk <mtk.manpages@gmail.com>
|
||||
.\" Added notes on differences from other Unix systems with respect to
|
||||
.\" Added notes on differences from other UNIX systems with respect to
|
||||
.\" waited-for children.
|
||||
.TH CLOCK 3 2008-08-28 "GNU" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
|
|
|
@ -35,7 +35,7 @@ These macros are used to create and access control messages (also called
|
|||
ancillary data) that are not a part of the socket payload.
|
||||
This control information may
|
||||
include the interface the packet was received on, various rarely used header
|
||||
fields, an extended error description, a set of file descriptors or Unix
|
||||
fields, an extended error description, a set of file descriptors or UNIX
|
||||
credentials.
|
||||
For instance, control messages can be used to send
|
||||
additional header fields such as IP options.
|
||||
|
@ -185,7 +185,7 @@ if (cmsg == NULL) {
|
|||
.fi
|
||||
.in
|
||||
.PP
|
||||
The code below passes an array of file descriptors over a Unix socket using
|
||||
The code below passes an array of file descriptors over a UNIX socket using
|
||||
.BR SCM_RIGHTS :
|
||||
.PP
|
||||
.in +4n
|
||||
|
|
|
@ -47,7 +47,7 @@ initialized data segment.
|
|||
This is the first address past the end of the
|
||||
uninitialized data segment (also known as the BSS segment).
|
||||
.SH CONFORMING TO
|
||||
Although these symbols have long been provided on most Unix systems,
|
||||
Although these symbols have long been provided on most UNIX systems,
|
||||
they are not standardized; use with caution.
|
||||
.SH NOTES
|
||||
The program must explicitly declare these symbols;
|
||||
|
|
|
@ -98,7 +98,7 @@ is identical to
|
|||
The advantage of the
|
||||
.BR byteorder (3)
|
||||
functions is that they are standard functions available
|
||||
on all Unix systems.
|
||||
on all UNIX systems.
|
||||
On the other hand, the fact that they were designed
|
||||
for use in the context of TCP/IP means that
|
||||
they lack the 64-bit and little-endian variants described in this page.
|
||||
|
|
|
@ -523,7 +523,7 @@ instead of including
|
|||
.IR <errno.h> .
|
||||
.BR "Do not do this" .
|
||||
It will not work with modern versions of the C library.
|
||||
However, on (very) old Unix systems, there may be no
|
||||
However, on (very) old UNIX systems, there may be no
|
||||
.I <errno.h>
|
||||
and the declaration is needed.
|
||||
.SH "SEE ALSO"
|
||||
|
|
|
@ -100,7 +100,7 @@ The use of
|
|||
and
|
||||
.B EXIT_FAILURE
|
||||
is slightly more portable
|
||||
(to non-Unix environments) than the use of 0 and some nonzero value
|
||||
(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
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification
|
||||
.\" OpenGroup's Single UNIX specification
|
||||
.\" http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification
|
||||
.\" OpenGroup's Single UNIX specification
|
||||
.\" http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
|
|
|
@ -111,7 +111,7 @@ and has no effect; the \(aqb\(aq is ignored on all POSIX
|
|||
conforming systems, including Linux.
|
||||
(Other systems may treat text files and binary files differently,
|
||||
and adding the \(aqb\(aq may be a good idea if you do I/O to a binary
|
||||
file and expect that your program may be ported to non-Unix
|
||||
file and expect that your program may be ported to non-UNIX
|
||||
environments.)
|
||||
.PP
|
||||
See NOTES below for details of glibc extensions for
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH FPUTWC 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH FPUTWS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -110,7 +110,7 @@ and
|
|||
setting and storing the current value of the file offset into or from the
|
||||
object referenced by
|
||||
.IR pos .
|
||||
On some non-Unix systems an
|
||||
On some non-UNIX systems an
|
||||
.I fpos_t
|
||||
object may be a complex object and these routines may be the only way to
|
||||
portably reposition a text stream.
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH FWIDE 3 2010-09-20 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -109,7 +109,7 @@ Upon failure or end-of-file, these functions return NULL and 0, respectively.
|
|||
.SH "CONFORMING TO"
|
||||
These functions are not in POSIX.1-2001.
|
||||
Several operating systems have them,
|
||||
e.g., *BSD, SunOS, Digital Unix, AIX (which also has a
|
||||
e.g., *BSD, SunOS, Digital UNIX, AIX (which also has a
|
||||
.BR getfstype ()).
|
||||
HP-UX has functions of the same names,
|
||||
that however use a \fIstruct checklist\fP
|
||||
|
|
|
@ -206,7 +206,7 @@ One might argue that according to POSIX
|
|||
.I errno
|
||||
should be left unchanged if an entry is not found.
|
||||
Experiments on various
|
||||
Unix-like systems shows that lots of different values occur in this
|
||||
UNIX-like systems shows that lots of different values occur in this
|
||||
situation: 0, ENOENT, EBADF, ESRCH, EWOULDBLOCK, EPERM and probably others.
|
||||
.\" more precisely:
|
||||
.\" AIX 5.1 - gives ESRCH
|
||||
|
|
|
@ -58,7 +58,7 @@ _BSD_SOURCE || (_XOPEN_SOURCE && _XOPEN_SOURCE\ <\ 500)
|
|||
and
|
||||
.BR sethostid ()
|
||||
respectively get or set a unique 32-bit identifier for the current machine.
|
||||
The 32-bit identifier is intended to be unique among all Unix systems in
|
||||
The 32-bit identifier is intended to be unique among all UNIX systems in
|
||||
existence.
|
||||
This normally resembles the Internet address for the local
|
||||
machine, as returned by
|
||||
|
|
|
@ -259,7 +259,7 @@ RFC\ 2553.
|
|||
.SH NOTES
|
||||
These functions were present in glibc 2.1.91-95, but were
|
||||
removed again.
|
||||
Several Unix-like systems support them, but all
|
||||
Several UNIX-like systems support them, but all
|
||||
call them deprecated.
|
||||
.SH "SEE ALSO"
|
||||
.BR getaddrinfo (3),
|
||||
|
|
|
@ -186,7 +186,7 @@ differs, and the returned structure is different.
|
|||
Under System V
|
||||
.I /etc/mnttab
|
||||
is used.
|
||||
4.4BSD and Digital Unix have a routine
|
||||
4.4BSD and Digital UNIX have a routine
|
||||
.BR getmntinfo (),
|
||||
a wrapper around the system call
|
||||
.BR getfsstat ().
|
||||
|
|
|
@ -212,7 +212,7 @@ One might argue that according to POSIX
|
|||
.I errno
|
||||
should be left unchanged if an entry is not found.
|
||||
Experiments on various
|
||||
Unix-like systems show that lots of different values occur in this
|
||||
UNIX-like systems show that lots of different values occur in this
|
||||
situation: 0, ENOENT, EBADF, ESRCH, EWOULDBLOCK, EPERM and probably others.
|
||||
.\" more precisely:
|
||||
.\" AIX 5.1 - gives ESRCH
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification
|
||||
.\" OpenGroup's Single UNIX specification
|
||||
.\" http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
|
|
|
@ -54,7 +54,7 @@ is provided in glibc since version 2.1.
|
|||
.SH "CONFORMING TO"
|
||||
POSIX.1-2001.
|
||||
.SH NOTES
|
||||
This is part of the Unix98 pty support, see
|
||||
This is part of the UNIX 98 pty support, see
|
||||
.BR pts (4).
|
||||
Many systems implement this function via a set-user-ID helper binary
|
||||
called "pt_chown".
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
.\"
|
||||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" OpenGroup's Single Unix specification
|
||||
.\" OpenGroup's Single UNIX specification
|
||||
.\" http://www.UNIX-systems.org/online.html
|
||||
.\"
|
||||
.\" 2000-06-30 correction by Yuichi SATO <sato@complex.eng.hokudai.ac.jp>
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
.\"
|
||||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\"
|
||||
.TH ICONV_CLOSE 3 2008-08-11 "GNU" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
.\"
|
||||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" OpenGroup's Single Unix specification
|
||||
.\" OpenGroup's Single UNIX specification
|
||||
.\" http://www.UNIX-systems.org/online.html
|
||||
.\"
|
||||
.\" 2007-03-31 Bruno Haible, Describe the glibc/libiconv //TRANSLIT
|
||||
|
|
|
@ -117,7 +117,7 @@ is defined before
|
|||
including \fI<search.h>\fP.
|
||||
|
||||
The location of the prototypes for these functions differs among several
|
||||
versions of Unix.
|
||||
versions of UNIX.
|
||||
The above is the POSIX version.
|
||||
Some systems place them in \fI<string.h>\fP.
|
||||
Linux libc4 and libc 5 placed them
|
||||
|
|
|
@ -83,7 +83,7 @@ For further information on feature test macros, see
|
|||
.\" Various special libraries. The manual pages documenting their functions
|
||||
.\" specify the library names.
|
||||
.SH "CONFORMING TO"
|
||||
Certain terms and abbreviations are used to indicate Unix variants
|
||||
Certain terms and abbreviations are used to indicate UNIX variants
|
||||
and standards to which calls in this section conform.
|
||||
See
|
||||
.BR standards (7).
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWALNUM 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWALPHA 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWBLANK 3 2010-09-20 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWCNTRL 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWCTYPE 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWDIGIT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWGRAPH 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWLOWER 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWPRINT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWPUNCT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWSPACE 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWUPPER 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH ISWXDIGIT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -202,7 +202,7 @@ are unaffected by the
|
|||
resource limit (see
|
||||
.BR getrlimit (2)).
|
||||
|
||||
The Unix98 standard requires
|
||||
The UNIX 98 standard requires
|
||||
.BR malloc (),
|
||||
.BR calloc (),
|
||||
and
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH MBLEN 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
@ -50,7 +50,7 @@ also returns \-1.
|
|||
If \fIs\fP is a NULL pointer, the
|
||||
.BR mblen ()
|
||||
function
|
||||
.\" The Dinkumware doc and the Single Unix specification say this, but
|
||||
.\" The Dinkumware doc and the Single UNIX specification say this, but
|
||||
.\" glibc doesn't implement this.
|
||||
resets the shift state, only known to this function, to the initial state, and
|
||||
returns nonzero if the encoding has nontrivial shift state, or zero if the
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH MBRLEN 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification
|
||||
.\" OpenGroup's Single UNIX specification
|
||||
.\" http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH MBSINIT 3 2000-11-20 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\"
|
||||
.TH MBSNRTOWCS 3 2010-09-15 "GNU" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH MBSRTOWCS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH MBSTOWCS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
.TH MBTOWC 3 2001-07-04 "GNU" "Linux Programmer's Manual"
|
||||
|
@ -55,7 +55,7 @@ ignored.
|
|||
The
|
||||
.BR mbtowc ()
|
||||
function
|
||||
.\" The Dinkumware doc and the Single Unix specification say this, but
|
||||
.\" The Dinkumware doc and the Single UNIX specification say this, but
|
||||
.\" glibc doesn't implement this.
|
||||
resets the shift state, only known to this function,
|
||||
to the initial state, and
|
||||
|
|
|
@ -188,7 +188,7 @@ and
|
|||
are glibc extensions.
|
||||
.SH NOTES
|
||||
The old behavior of creating a file with mode 0666 may be
|
||||
a security risk, especially since other Unix flavors use 0600,
|
||||
a security risk, especially since other UNIX flavors use 0600,
|
||||
and somebody might overlook this detail when porting programs.
|
||||
|
||||
More generally, the POSIX specification of
|
||||
|
|
|
@ -92,7 +92,7 @@ POSIX.1-2008 removes the specification of
|
|||
.SH NOTES
|
||||
The prototype is in
|
||||
.I <unistd.h>
|
||||
for libc4, libc5, glibc1; glibc2 follows the Single Unix Specification
|
||||
for libc4, libc5, glibc1; glibc2 follows the Single UNIX Specification
|
||||
and has the prototype in
|
||||
.IR <stdlib.h> .
|
||||
.SH BUGS
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
.\"
|
||||
.\" References consulted:
|
||||
.\" GNU glibc-2 manual
|
||||
.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
|
||||
.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
|
||||
.\"
|
||||
.\" Corrected prototype, 2002-10-18, aeb
|
||||
.\"
|
||||
|
|
|
@ -161,7 +161,7 @@ In versions of glibc before 2.0.92,
|
|||
.BR openpty ()
|
||||
returns file descriptors for a BSD pseudo-terminal pair;
|
||||
since glibc 2.0.92,
|
||||
it first attempts to open a Unix 98 pseudo-terminal pair,
|
||||
it first attempts to open a UNIX 98 pseudo-terminal pair,
|
||||
and falls back to opening a BSD pseudo-terminal pair if that fails.
|
||||
.SH BUGS
|
||||
Nobody knows how much space should be reserved for
|
||||
|
|
|
@ -76,13 +76,13 @@ Glibc support for
|
|||
has been provided since version 2.2.1.
|
||||
.SH "CONFORMING TO"
|
||||
.BR posix_openpt ()
|
||||
is part of the Unix98 pseudo-terminal support (see
|
||||
is part of the UNIX 98 pseudo-terminal support (see
|
||||
.BR pts (4)).
|
||||
This function is specified in POSIX.1-2001.
|
||||
.SH NOTES
|
||||
This function is a recent invention in POSIX.
|
||||
Some Unix implementations that support System V
|
||||
(aka Unix 98) pseudo-terminals don't have this function, but it
|
||||
Some UNIX implementations that support System V
|
||||
(aka UNIX 98) pseudo-terminals don't have this function, but it
|
||||
is easy to implement:
|
||||
.in +4n
|
||||
.nf
|
||||
|
|
|
@ -225,7 +225,7 @@ are equivalent.
|
|||
The second style allows repeated references to the
|
||||
same argument.
|
||||
The C99 standard does not include the style using \(aq$\(aq,
|
||||
which comes from the Single Unix Specification.
|
||||
which comes from the Single UNIX Specification.
|
||||
If the style using
|
||||
\(aq$\(aq is used, it must be used throughout for all conversions taking an
|
||||
argument and all width and precision arguments, but it may be mixed
|
||||
|
@ -896,7 +896,7 @@ since glibc version 2.1.
|
|||
Until glibc 2.0.6 they would return \-1
|
||||
when the output was truncated.
|
||||
.\" .SH HISTORY
|
||||
.\" Unix V7 defines the three routines
|
||||
.\" UNIX V7 defines the three routines
|
||||
.\" .BR printf (),
|
||||
.\" .BR fprintf (),
|
||||
.\" .BR sprintf (),
|
||||
|
|
|
@ -77,7 +77,7 @@ is too small.
|
|||
is provided in glibc since version 2.1.
|
||||
.SH "CONFORMING TO"
|
||||
.BR ptsname ()
|
||||
is part of the Unix98 pseudo-terminal support (see
|
||||
is part of the UNIX 98 pseudo-terminal support (see
|
||||
.BR pts (4)).
|
||||
This function is specified in POSIX.1-2001.
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
.\" References consulted:
|
||||
.\" GNU glibc-2 source code and manual
|
||||
.\" Dinkumware C library reference http://www.dinkumware.com/
|
||||
.\" OpenGroup's Single Unix specification
|
||||
.\" OpenGroup's Single UNIX specification
|
||||
.\" http://www.UNIX-systems.org/online.html
|
||||
.\" ISO/IEC 9899:1999
|
||||
.\"
|
||||
|
|
|
@ -69,7 +69,7 @@ and
|
|||
.BR gcvt (3).
|
||||
.SH "CONFORMING TO"
|
||||
SVr4.
|
||||
Not seen in most common Unix implementations,
|
||||
Not seen in most common UNIX implementations,
|
||||
but occurs in SunOS.
|
||||
Not supported by libc4 and libc5.
|
||||
Supported by glibc.
|
||||
|
|
|
@ -121,7 +121,7 @@ in
|
|||
.IR *fd2p .
|
||||
The control process will return diagnostic
|
||||
output from the command (unit 2) on this channel, and will also
|
||||
accept bytes on this channel as being Unix signal numbers, to be
|
||||
accept bytes on this channel as being UNIX signal numbers, to be
|
||||
forwarded to the process group of the command.
|
||||
If
|
||||
.I fd2p
|
||||
|
|
|
@ -193,7 +193,7 @@ This is a symbolic link.
|
|||
This is a regular file.
|
||||
.TP
|
||||
.B DT_SOCK
|
||||
This is a Unix domain socket.
|
||||
This is a UNIX domain socket.
|
||||
.TP
|
||||
.B DT_UNKNOWN
|
||||
The file type is unknown.
|
||||
|
|
|
@ -97,9 +97,7 @@ in
|
|||
.IR *fd2p .
|
||||
The control process will return diagnostic
|
||||
output from the command (unit 2) on this channel, and will also
|
||||
accept bytes on this channel as being
|
||||
Unix
|
||||
signal numbers, to be
|
||||
accept bytes on this channel as being UNIX signal numbers, to be
|
||||
forwarded to the process group of the command.
|
||||
The diagnostic
|
||||
information returned does not include remote authorization failure,
|
||||
|
|
|
@ -1009,7 +1009,7 @@ RPC-style messages without using the RPC package.
|
|||
.BI "bool_t xdr_authunix_parms(XDR *" xdrs ", struct authunix_parms *" aupp );
|
||||
.fi
|
||||
.IP
|
||||
Used for describing Unix credentials.
|
||||
Used for describing UNIX credentials.
|
||||
This routine is useful for users
|
||||
who wish to generate these credentials without using the RPC
|
||||
authentication package.
|
||||
|
|
|
@ -91,7 +91,7 @@ These functions are not in POSIX.1-2001, but
|
|||
.BR getnetgrent (),
|
||||
and
|
||||
.BR innetgr ()
|
||||
are available on most Unix systems.
|
||||
are available on most UNIX systems.
|
||||
.BR getnetgrent_r ()
|
||||
is not widely available on other systems.
|
||||
.\" getnetgrent_r() is on Solaris 8 and AIX 5.1, but not the BSDs.
|
||||
|
|
|
@ -260,7 +260,7 @@ and
|
|||
.B O_TRUNC
|
||||
unspecified.
|
||||
On Linux, this will successfully truncate an existing
|
||||
shared memory object \(em this may not be so on other Unix systems.
|
||||
shared memory object \(em this may not be so on other UNIX systems.
|
||||
.LP
|
||||
The POSIX shared memory object implementation on Linux 2.4 makes use
|
||||
of a dedicated file system, which is normally
|
||||
|
|
|
@ -29,7 +29,7 @@ sigpause \- atomically release blocked signals and wait for interrupt
|
|||
.sp
|
||||
.BI "int sigpause(int " sigmask "); /* BSD */"
|
||||
.sp
|
||||
.BI "int sigpause(int " sig "); /* System V / Unix95 */"
|
||||
.BI "int sigpause(int " sig "); /* System V / UNIX 95 */"
|
||||
.fi
|
||||
.SH DESCRIPTION
|
||||
Don't use this function.
|
||||
|
@ -60,11 +60,11 @@ is standardized in POSIX.1-2001.
|
|||
The classical BSD version of this function appeared in 4.2BSD.
|
||||
It sets the process's signal mask to
|
||||
.IR sigmask .
|
||||
Unix95 standardized the incompatible System V version of
|
||||
UNIX 95 standardized the incompatible System V version of
|
||||
this function, which removes only the specified signal
|
||||
.I sig
|
||||
from the process's signal mask.
|
||||
.\" __xpg_sigpause: Unix 95, spec 1170, SVID, SVr4, XPG
|
||||
.\" __xpg_sigpause: UNIX 95, spec 1170, SVID, SVr4, XPG
|
||||
The unfortunate situation with two incompatible functions with the
|
||||
same name was solved by the
|
||||
.BR \%sigsuspend (2)
|
||||
|
|
|
@ -18,7 +18,7 @@ stdin, stdout, stderr \- standard I/O streams
|
|||
.BI "extern FILE *" stderr ;
|
||||
.fi
|
||||
.SH DESCRIPTION
|
||||
Under normal circumstances every Unix program has three streams opened
|
||||
Under normal circumstances every UNIX program has three streams opened
|
||||
for it when it starts up, one for input, one for output, and one for
|
||||
printing diagnostic or error messages.
|
||||
These are typically attached to
|
||||
|
@ -50,8 +50,8 @@ or
|
|||
.PP
|
||||
Since
|
||||
.IR FILE s
|
||||
are a buffering wrapper around Unix file descriptors, the
|
||||
same underlying files may also be accessed using the raw Unix file
|
||||
are a buffering wrapper around UNIX file descriptors, the
|
||||
same underlying files may also be accessed using the raw UNIX file
|
||||
interface, that is, the functions like
|
||||
.BR read (2)
|
||||
and
|
||||
|
|
|
@ -65,7 +65,7 @@ returns a pointer to the \fBend\fP of the string
|
|||
rather than the beginning.
|
||||
.SH "CONFORMING TO"
|
||||
This function is not part of the C or POSIX.1 standards, and is
|
||||
not customary on Unix systems, but is not a GNU invention either.
|
||||
not customary on UNIX systems, but is not a GNU invention either.
|
||||
Perhaps it comes from MS-DOS.
|
||||
Nowadays, it is also present on the BSDs.
|
||||
.SH EXAMPLE
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue