.SH NAME
intro \- Introduction to user commands
.SH DESCRIPTION
-Linux is a flavour of Unix, and as a first approximation
+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
One types commands to the
.IR shell ,
the command interpreter. It is not built-in, but is just a program
-and you can change your shell. Everybody has her own favourite one.
+and you can change your shell. Everybody has her own favorite one.
The standard one is called
.IR sh .
See also
.BR tcflush (3)
before calling
.BR _exit ().
-Whether any pending I/O is cancelled, and which pending I/O may be
-cancelled upon
+Whether any pending I/O is canceled, and which pending I/O may be
+canceled upon
.BR _exit (),
is implementation-dependent.
.SH "SEE ALSO"
passes already-pending network errors on the new socket
as an error code from
.BR accept ().
-This behaviour differs from other BSD socket
+This behavior differs from other BSD socket
implementations.
For reliable operation the application should detect
the network errors defined for the protocol after
and
.BR O_ASYNC
from the listening socket.
-This behaviour differs from the canonical BSD sockets implementation.
+This behavior differs from the canonical BSD sockets implementation.
.\" Some testing seems to show that Tru64 5.1 and HP-UX 11 also
.\" do not inherit file status flags -- MTK Jun 05
Portable programs should not rely on inheritance or non-inheritance
the underlying file system.
Since kernel 2.6.20,
.BR access ()
-honours this flag.
+honors this flag.
.SH "SEE ALSO"
.BR chmod (2),
.BR chown (2),
In any event any previously set
.BR alarm ()
-is cancelled.
+is canceled.
.SH "RETURN VALUE"
.BR alarm ()
returns the number of seconds remaining until any previously scheduled
.SS Linux Notes
The return value described above for
.BR brk ()
-is the behaviour provided by the glibc wrapper function for the Linux
+is the behavior provided by the glibc wrapper function for the Linux
.BR brk ()
system call.
(On most other implementations, the return value from
POSIX does not specify whether
this also should happen when root does the
.BR chown ();
-the Linux behaviour depends on the kernel version.
+the Linux behavior depends on the kernel version.
.\" In Linux 2.0 kernels, superuser was like everyone else
.\" In 2.2, up to 2.2.12, these bits were not cleared for superuser.
.\" Since 2.2.13, superuser is once more like everyone else.
.\" Renamed "__clone" to "clone" (which is the prototype in <sched.h>)
.\" various other minor tidy ups and clarifications.
.\" Modified 26 Jun 2001 by Michael Kerrisk <mtk-manpages@gmx.net>
-.\" Updated notes for 2.4.7+ behaviour of CLONE_THREAD
+.\" Updated notes for 2.4.7+ behavior of CLONE_THREAD
.\" Modified 15 Oct 2002 by Michael Kerrisk <mtk-manpages@gmx.net>
.\" Added description for CLONE_NEWNS, which was added in 2.4.19
.\" Slightly rephrased, aeb.
.\" Modified 1 Feb 2003 - added CLONE_SIGHAND restriction, aeb.
.\" Modified 1 Jan 2004 - various updates, aeb
.\" Modified 2004-09-10 - added CLONE_PARENT_SETTID etc - aeb.
-.\" 2005-04-12, mtk, noted the PID caching behaviour of NPTL's getpid()
+.\" 2005-04-12, mtk, noted the PID caching behavior of NPTL's getpid()
.\" wrapper under BUGS.
.\" 2005-05-10, mtk, added CLONE_SYSVSEM, CLONE_UNTRACED, CLONE_STOPPED.
.\" 2005-05-17, mtk, Substantially enhanced discussion of CLONE_THREAD.
.IR events .
.TP
.B EPOLLET
-Sets the Edge Triggered behaviour for the associated file descriptor.
-The default behaviour for
+Sets the Edge Triggered behavior for the associated file descriptor.
+The default behavior for
.B epoll
is Level Triggered.
See
distribution architectures.
.TP
.BR EPOLLONESHOT " (since kernel 2.6.2)"
-Sets the one-shot behaviour for the associated file descriptor.
+Sets the one-shot behavior for the associated file descriptor.
This means that after an event is pulled out with
.BR epoll_wait (2)
the associated file descriptor is internally disabled and no other events
then an implementation may leave the disposition unchanged or
reset it to the default; Linux does the former.
.IP * 4
-Any outstanding asynchronous I/O operations are cancelled
+Any outstanding asynchronous I/O operations are canceled
.RB ( aio_read (3),
.BR aio_write (3)).
.IP * 4
An ELF interpreter was a directory.
.TP
.B ELIBBAD
-An ELF interpreter was not in a recognised format.
+An ELF interpreter was not in a recognized format.
.TP
.B ELOOP
Too many symbolic links were encountered in resolving
needed for file or interpreter cannot be found.
.TP
.B ENOEXEC
-An executable is not in a recognised format, is for the wrong
+An executable is not in a recognized format, is for the wrong
architecture, or has some other format error that means it cannot be
executed.
.TP
.\" Modified 2004-12-08, added O_NOATIME after note from Martin Pool
.\" 2004-12-10, mtk, noted F_GETOWN bug after suggestion from aeb.
.\" 2005-04-08 Jamie Lokier <jamie@shareable.org>, mtk
-.\" Described behaviour of F_SETOWN/F_SETSIG in
+.\" Described behavior of F_SETOWN/F_SETSIG in
.\" multi-threaded processes, and generally cleaned
.\" up the discussion of F_SETOWN.
.\" 2005-05-20, Johannes Nicolai <johannes.nicolai@hpi.uni-potsdam.de>,
.TP
.B F_GETSIG
Value of signal sent when read or write becomes possible, or zero
-for traditional SIGIO behaviour.
+for traditional SIGIO behavior.
.TP
All other commands
Zero.
with the result that the conversion either blocks, or fails if
.B LOCK_NB
was specified.
-(This is the original BSD behaviour,
+(This is the original BSD behavior,
and occurs on many other implementations.)
.\" Kernel 2.5.21 changed things a little: during lock conversion
.\" it is now the highest priority process that will get the lock -- mtk
.RB ( mlock (2),
.BR mlockall (2)).
.IP * 4
-Process resource utilisations
+Process resource utilizations
.RB ( getrusage (2))
and CPU time counters
.RB ( times (2))
The aim of
.BR fdatasync (2)
is to reduce disk activity for applications that do not
-require all metadata to be synchronised with the disk.
+require all metadata to be synchronized with the disk.
.SH "RETURN VALUE"
On success, zero is returned.
On error, \-1 is returned, and
.\" Håvard Lygre <hklygre@online.no>
.\" Modified 2001-04-17 by Michael Kerrisk <mtk-manpages@gmx.net>
.\" Modified 2002-06-13 by Michael Kerrisk <mtk-manpages@gmx.net>
-.\" Added note on non-standard behaviour when SIGCHLD is ignored.
+.\" Added note on non-standard behavior when SIGCHLD is ignored.
.\" Modified 2002-07-09 by Michael Kerrisk <mtk-manpages@gmx.net>
.\" Enhanced descriptions of 'resource' values for [gs]etrlimit()
.\" Modified 2003-11-28 by aeb, added RLIMIT_CORE
once per second until the hard limit is reached, at which time
it is sent
.BR SIGKILL .
-(This latter point describes Linux 2.2 through 2.6 behaviour.
+(This latter point describes Linux 2.2 through 2.6 behavior.
Implementations vary in how they treat processes which continue to
consume CPU time after reaching the soft limit.
Portable applications that need to catch this signal should
.BR io_cancel ()
attempts to cancel an asynchronous I/O operation previously submitted with
.BR io_submit (2).
-\fIctx_id\fR is the AIO context ID of the operation to be cancelled.
-If the AIO context is found, the event will be cancelled and then copied
+\fIctx_id\fR is the AIO context ID of the operation to be canceled.
+If the AIO context is found, the event will be canceled and then copied
into the memory pointed to by \fIresult\fR without being placed
into the completion queue.
.SH "RETURN VALUE"
One of the data structures points to invalid data.
.TP
.B EAGAIN
-The \fIiocb\fR specified was not cancelled.
+The \fIiocb\fR specified was not canceled.
.TP
.B ENOSYS
.BR io_cancel ()
(POSIX says: If
.I pgrp
-is less than or equal to 1, the behaviour is undefined.)
+is less than or equal to 1, the behavior is undefined.)
For a process to have permission to send a signal
it must either be privileged (under Linux: have the
.BR listen ()
function call first appeared in 4.2BSD.
.SH NOTES
-The behaviour of the
+The behavior of the
.I backlog
parameter on TCP sockets changed with Linux 2.2.
Now it specifies the queue length for
.BR MADV_DOFORK " (Since Linux 2.6.16)"
Undo the effect of
.BR MADV_DONTFORK ,
-restoring the default behaviour, whereby a mapping is inherited across
+restoring the default behavior, whereby a mapping is inherited across
.BR fork (2).
.SH "RETURN VALUE"
On success
POSIX.1-2001 describes
.BR posix_madvise (3)
with constants POSIX_MADV_NORMAL, etc.,
-with a behaviour close to that described here.
+with a behavior close to that described here.
There is a similar
.BR posix_fadvise (3)
for file access.
more as a command than as advice and hence may return an error
when it cannot do what it usually would do in response to this
advice. (See the ERRORS description above.)
-This is nonstandard behaviour.
+This is nonstandard behavior.
.LP
The Linux implementation requires that the address
.I start
.\" 1993 Michael Haardt
.\" 1993,1994 Ian Jackson.
.\" You may distribute it under the terms of the GNU General
-.\" Public Licence. It comes with NO WARRANTY.
+.\" Public License. It comes with NO WARRANTY.
.\"
.TH MKDIR 2 2003-12-09 "Linux" "Linux Programmer's Manual"
.SH NAME
.\" 1993 Michael Haardt
.\" 1993,1994 Ian Jackson.
.\" You may distribute it under the terms of the GNU General
-.\" Public Licence. It comes with NO WARRANTY.
+.\" Public License. It comes with NO WARRANTY.
.\"
.\" Modified 1996-08-18 by urs
.\" Modified 2003-04-23 by Michael Kerrisk
The contents of a file mapping (as opposed to an anonymous mapping; see
.B MAP_ANONYMOUS
-below), are initialised using
+below), are initialized using
.I length
bytes starting at offset
.I offset
argument determines whether updates to the mapping
are visible to other processes mapping the same region,
and whether updates are caried through to the underlying file.
-This behaviour is determined by including exactly one
+This behavior is determined by including exactly one
of the following values in
.IR flags :
.TP 1.1i
.TP
.B MAP_ANONYMOUS
The mapping is not backed by any file;
-its contents are initialised to zero.
+its contents are initialized to zero.
The
.I fd
and
.B MAP_DENYWRITE
This flag is ignored.
.\" Introduced in 1.1.36, removed in 1.3.24.
-(Long ago, it signalled that attempts to write to the underlying file
+(Long ago, it signaled that attempts to write to the underlying file
should fail with
.BR ETXTBUSY .
But this was a source of denial-of-service attacks.)
.B MAP_EXECUTABLE
This flag is ignored.
.\" Introduced in 1.1.38, removed in 1.3.24. Flag tested in proc_follow_link.
-.\" (Long ago, it signalled that the underlying file is an executable.
+.\" (Long ago, it signaled that the underlying file is an executable.
.\" However, that information was not really used anywhere.)
.\" Linus talked about DOS related to MAP_EXECUTABLE, but he was thinking of
.\" MAP_DENYWRITE?
.\"
.\" Modified 1996-11-04 by Eric S. Raymond <esr@thyrsus.com>
.\" Modified 2001-10-13 by Michael Kerrisk <mtk-manpages@gmx.net>
-.\" Added note on historical behaviour of MS_NOSUID
+.\" Added note on historical behavior of MS_NOSUID
.\" Modified 2002-05-16 by Michael Kerrisk <mtk-manpages@gmx.net>
.\" Extensive changes and additions
.\" Modified 2002-05-27 by aeb
.\" users cannot execute files uploaded using ftp or so.)
.TP
.B MS_NOSUID
-Do not honour set-user-ID and set-group-ID bits when executing
+Do not honor set-user-ID and set-group-ID bits when executing
programs from this file system.
.\" (This is a security feature to prevent users executing set-user-ID and
.\" set-group-ID programs from removable disk devices.)
.BR umount (),
unmounts a target, but allows additional
.I flags
-controlling the behaviour of the operation:
+controlling the behavior of the operation:
.TP
.BR MNT_FORCE " (since Linux 2.1.116)"
Force unmount even if busy.
SVr4, POSIX.1-2001.
.\" SVr4 defines an additional error
.\" code EAGAIN. The SVr4 error conditions don't map neatly onto Linux's.
-POSIX says that the behaviour of
+POSIX says that the behavior of
.BR mprotect ()
is unspecified if it is applied to a region of memory that
was not obtained via
.I msqid_ds
(see
.BR msgctl (2))
-is initialised as follows:
+is initialized as follows:
.IP
.I msg_perm.cuid
and
.\" Modified 1 Jun 2002, Michael Kerrisk <mtk-manpages@gmx.net>
.\" Language clean-ups.
.\" Enhanced and corrected information on msg_qbytes, MSGMNB and MSGMAX
-.\" Added note on restart behaviour of msgsnd() and msgrcv()
+.\" Added note on restart behavior of msgsnd() and msgrcv()
.\" Formatting clean-ups (argument and field names marked as .I
.\" instead of .B)
.\" Modified, 27 May 2004, Michael Kerrisk <mtk-manpages@gmx.net>
(The queue capacity is defined by the
.I msg_bytes
field in the associated data structure for the message queue.
-During queue creation this field is initialised to
+During queue creation this field is initialized to
.B MSGMNB
bytes, but this limit can be modified using
.BR msgctl (2).)
If insufficient space is available in the queue, then the default
-behaviour of
+behavior of
.BR msgsnd ()
is to block until space becomes available.
If
argument.
If the message text has length greater than
.IR msgsz ,
-then the behaviour depends on whether
+then the behavior depends on whether
.BR MSG_NOERROR
is specified in
.IR msgflg .
For the same reason, the value returned in case of a delivered
signal in *\fIrem\fR is usually rounded to the next larger multiple of
1/\fIHZ\fR\ s.
-.SS "Old behaviour"
+.SS "Old behavior"
In order to support applications requiring much more precise pauses
(e.g., in order to control some time-critical hardware),
.BR nanosleep ()
amongst others
.BR O_SYNC " and " O_NDELAY .
-POSIX provides for three different variants of synchronised I/O,
+POSIX provides for three different variants of synchronized I/O,
corresponding to the flags \fBO_SYNC\fR, \fBO_DSYNC\fR and
\fBO_RSYNC\fR.
Currently (2.1.130) these are all synonymous under Linux.
system call modifies its
.I timeout
argument.
-However, the glibc wrapper function hides this behaviour
+However, the glibc wrapper function hides this behavior
by using a local variable for the timeout argument that
is passed to the system call.
Thus, the glibc
.BR posix_fadvise ()
to announce an intention to access
file data in a specific pattern in the future, thus allowing the kernel
-to perform appropriate optimisations.
+to perform appropriate optimizations.
The \fIadvice\fP applies to a (not necessarily existent) region starting
at \fIoffset\fP and extending for \fIlen\fP bytes (or until the end of
.B PR_SET_DUMPABLE
(Since Linux 2.3.20)
Set the state of the flag determining whether core dumps are produced
-for this process upon delivery of a signal whose default behaviour is
+for this process upon delivery of a signal whose default behavior is
to produce a core dump.
(Normally this flag is set for a process by default, but it is cleared
when a set-user-ID or set-group-ID program is executed and also by
this policy will cause the scheduler to always assume
that the process is CPU-intensive.
Consequently, the scheduler will apply a small scheduling
-penalty so that this process is mildly disfavoured in scheduling
+penalty so that this process is mildly disfavored in scheduling
decisions.
.\" The following paragraph is drawn largely from the text that
.\" accompanied Ingo Molnar's patch for the implementation of
.I timeout
to reflect the amount of time not slept; most other implementations
do not do this.
-(POSIX.1-2001 permits either behaviour.)
+(POSIX.1-2001 permits either behavior.)
This causes problems both when Linux code which reads
.I timeout
is ported to other operating systems, and when code is ported to Linux
to be undefined after
.BR select ()
returns.
-.\" .PP - it is rumoured that:
+.\" .PP - it is rumored that:
.\" On BSD, when a timeout occurs, the file descriptor bits are not changed.
.\" - it is certainly true that:
.\" Linux follows SUSv2 and sets the bit masks to zero upon a timeout.
system call modifies its
.I timeout
argument.
-However, the glibc wrapper function hides this behaviour
+However, the glibc wrapper function hides this behavior
by using a local variable for the timeout argument that
is passed to the system call.
Thus, the glibc
.BR pselect ()
function does not modify its timeout argument;
-this is the behaviour required by POSIX.1-2001.
+this is the behavior required by POSIX.1-2001.
.SH BUGS
Glibc 2.0 provided a version of
.BR pselect ()
.\" Modified, 11 Nov 2004, Michael Kerrisk <mtk-manpages@gmx.net>
.\" Language and formatting clean-ups
.\" Added notes on /proc files
-.\" Rewrote BUGS note about semget()'s failure to initialise
+.\" Rewrote BUGS note about semget()'s failure to initialize
.\" semaphore values
.\"
.TH SEMGET 2 2004-05-27 "Linux" "Linux Programmer's Manual"
The values of the semaphores in a newly created set are indeterminate.
(POSIX.1-2001 is explicit on this point.)
Although Linux, like many other implementations,
-initialises the semaphore values to 0,
+initializes the semaphore values to 0,
a portable application cannot rely on this:
-it should explicitly initialise the semaphores to the desired values.
+it should explicitly initialize the semaphores to the desired values.
.\" In truth, every one of the many implementations that I've tested sets
.\" the values to zero, but I suppose there is/was some obscure
.\" implementation out there that does not.
.PP
When creating a new semaphore set,
.BR semget ()
-initialises the set's associated data structure,
+initializes the set's associated data structure,
.I semid_ds
(see
.BR semctl (2)),
The name choice IPC_PRIVATE was perhaps unfortunate, IPC_NEW
would more clearly show its function.
.LP
-The semaphores in a set are not initialised by
+The semaphores in a set are not initialized by
.BR semget ().
-.\" In fact they are initialised to zero on Linux, but POSIX.1-2001
+.\" In fact they are initialized to zero on Linux, but POSIX.1-2001
.\" does not specify this, and we can't portably rely on it.
-In order to initialise the semaphores,
+In order to initialize the semaphores,
.BR semctl (2)
must be used to perform a
.B SETVAL
.B SETALL
operation on the semaphore set.
(Where multiple peers do not know who will be the first to
-initialise the set, checking for a non-zero
+initialize the set, checking for a non-zero
.I sem_otime
in the associated data structure retrieved by a
.BR semctl (2)
.IR atomically ,
that is, the operations are performed either as a complete unit,
or not at all.
-The behaviour of the system call if not all operations can be
+The behavior of the system call if not all operations can be
performed immediately depends on the presence of the
.B IPC_NOWAIT
flag in the individual
Tell the link layer that forward progress happened: you got a successful
reply from the other side.
If the link layer doesn't get this
-it will regularly reprobe the neighbour (e.g. via a unicast ARP).
+it will regularly reprobe the neighbor (e.g. via a unicast ARP).
Only valid on
.B SOCK_DGRAM
and
.\" Noted that CAP_IPC_LOCK is not required for SHM_UNLOCK
.\" since kernel 2.6.9
.\" Modified, 2004-11-25, mtk, notes on 2.6.9 RLIMIT_MEMLOCK changes
-.\" 2005-04-25, mtk -- noted aberrant Linux behaviour w.r.t. new
+.\" 2005-04-25, mtk -- noted aberrant Linux behavior w.r.t. new
.\" attaches to a segment that has already been marked for deletion.
.\" 2005-08-02, mtk: Added IPC_INFO, SHM_INFO, SHM_STAT descriptions.
.\"
.\" specified.
.PP
When a new shared memory segment is created,
-its contents are initialised to zero values, and
+its contents are initialized to zero values, and
its associated data structure,
.I shmid_ds
(see
.BR shmctl (2)),
-is initialised as follows:
+is initialized as follows:
.IP
.I shm_perm.cuid
and
.PP
On Linux, it is possible to attach a shared memory segment even if it
is already marked to be deleted.
-However, POSIX.1-2001 does not specify this behaviour and
+However, POSIX.1-2001 does not specify this behavior and
many other implementations do not support it.
.LP
The following system parameter affects
flag is used.
.PP
.I sa_flags
-specifies a set of flags which modify the behaviour of the signal handling
+specifies a set of flags which modify the behavior of the signal handling
process.
It is formed by the bitwise OR of zero or more of the following:
.RS
If an alternate stack is not available, the default stack will be used.
.TP
.B SA_RESTART
-Provide behaviour compatible with BSD signal semantics by making certain
+Provide behavior compatible with BSD signal semantics by making certain
system calls restartable across signals.
.TP
.B SA_NODEFER
.\" SVr4 does not document the EINTR condition.
.SH NOTES
.PP
-According to POSIX, the behaviour of a process is undefined after it
+According to POSIX, the behavior of a process is undefined after it
ignores a
.BR SIGFPE ,
.BR SIGILL ,
.B SIGCHLD
can be used to prevent the creation of zombies (see
.BR wait (2)).
-Nevertheless, the historical BSD and System V behaviours for ignoring
+Nevertheless, the historical BSD and System V behaviors for ignoring
.B SIGCHLD
differ, so that the only completely portable method of ensuring that
terminated children do not become zombies is to catch the
.sp
.BI "sighandler_t signal(int " signum ", sighandler_t " handler );
.SH DESCRIPTION
-The behaviour of
+The behavior of
.BR signal ()
varies across Unix versions,
and has also varied historically across different versions of Linux.
.BR signal ()
in a multi-threaded process are unspecified.
.PP
-According to POSIX, the behaviour of a process is undefined after it
+According to POSIX, the behavior of a process is undefined after it
ignores a
.BR SIGFPE ,
.BR SIGILL ,
(and the Linux kernel and libc4,5) does the same.
On the other hand, BSD does not reset the handler, but blocks
new instances of this signal from occurring during a call of the handler.
-The glibc2 library follows the BSD behaviour.
+The glibc2 library follows the BSD behavior.
If one on a libc5 system includes
.B "<bsd/signal.h>"
.B _XOPEN_SOURCE
or uses a separate
.BR sysv_signal (3)
-function, one obtains classical behaviour.
+function, one obtains classical behavior.
This is not recommended.
.SH "SEE ALSO"
.BR kill (1),
.SH DESCRIPTION
.BR sigprocmask ()
is used to change the signal mask, the set of currently blocked signals.
-The behaviour of the call is dependent on the value of
+The behavior of the call is dependent on the value of
.IR how ,
as follows.
.RS
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
-.\" added note on self-signalling, aeb, 2002-06-07
+.\" added note on self-signaling, aeb, 2002-06-07
.\" added note on CAP_KILL, mtk, 2004-06-16
.\"
.TH SIGQUEUE 2 2004-06-16 "Linux" "Linux Programmer's Manual"
Deleting the name referred to by a symlink will actually delete the
file (unless it also has other hard links).
-If this behaviour is not desired, use
+If this behavior is not desired, use
.BR link (2).
.SH "SEE ALSO"
.BR ln (1),
with disk.
.I offset
-is the starting byte of the file range to be synchronised.
+is the starting byte of the file range to be synchronized.
.I nbytes
-specifies the length of the range to be synchronised, in bytes; if
+specifies the length of the range to be synchronized, in bytes; if
.I nbytes
is zero, then all bytes from
.I offset
-through to the end of file are synchronised.
-Synchronisation is in units of the system page size:
+through to the end of file are synchronized.
+Synchronization is in units of the system page size:
.I offset
is rounded down to a page boundary;
.I (offset+nbytes-1)
different animals.
In libc4 and libc5 the number of this call was defined by
.BR SYS_klog .
-In glibc 2.0 the syscall is baptised
+In glibc 2.0 the syscall is baptized
.BR klogctl ().
.SH "SEE ALSO"
.BR syslog (3)
seconds are ignored and all years divisible by 4 are leap years.
This value is not the same as the actual number of seconds between the time
and the Epoch, because of leap seconds and because clocks are not
-required to be synchronised to a standard reference.
+required to be synchronized to a standard reference.
The intention is
that the interpretation of seconds since the Epoch values be
consistent; see POSIX.1 Annex B 2.2.2 for further rationale.
.\" Modified 961203 and 001211 and 010326 by aeb@cwi.nl
.\" Modified 001213 by Michael Haardt (michael@moria.de)
.\" Modified 13 Jun 02, Michael Kerrisk <mtk-manpages@gmx.net>
-.\" Added note on non-standard behaviour when SIGCHLD is ignored.
+.\" Added note on non-standard behavior when SIGCHLD is ignored.
.\" Modified 2004-11-16, mtk, Noted that the non-conformance when
.\" SIGCHLD is being ignored is fixed in 2.6.9; other minor changes
.\" Modified 2004-12-08, mtk, in 2.6 times() return value changed
.\" 2005-04-13, mtk
-.\" Added notes on non-standard behaviour: Linux allows 'buf' to
+.\" Added notes on non-standard behavior: Linux allows 'buf' to
.\" be NULL, but POSIX.1 doesn't specify this and it's non-portable.
.\"
.TH TIMES 2 2002-06-14 "Linux" "Linux Programmer's Manual"
argument can be specified as NULL, with the result that
.BR times ()
just returns a function result.
-However, POSIX does not specify this behaviour, and most
+However, POSIX does not specify this behavior, and most
other Unix implementations require a non-NULL value for
.IR buf .
.LP
except when the specified process is part of a thread group
(created by specifying the CLONE_THREAD flag in the call to clone).
Since all the processes in a thread group have the same PID,
-they cannot be individually signalled with
+they cannot be individually signaled with
.BR kill (2).
With
.BR tkill (),
call improves on
.BR tkill ()
by allowing the caller to
-specify the thread group ID of the thread to be signalled, protecting
+specify the thread group ID of the thread to be signaled, protecting
against TID reuse.
If the tgid is specified as \-1,
.BR tgkill ()
.SH NOTES
The above description is for XSI-compliant systems.
For non-XSI-compliant systems, the POSIX standard allows
-two behaviours for
+two behaviors for
.BR ftruncate ()
when
.I length
.BR vfork ()
function has the same effect as
.BR fork (2),
-except that the behaviour is undefined if the process created by
+except that the behavior is undefined if the process created by
.BR vfork ()
either modifies any data other than a variable of type
.I pid_t
.BR execve (2)
or
.BR _exit (2)
-and cannot rely on any specific behaviour w.r.t. shared memory.
+and cannot rely on any specific behavior w.r.t. shared memory.
.\" In AIXv3.1 vfork is equivalent to fork.
.SH NOTES
.SS Linux Notes
other architectures) it is an independent system call.
Support was added in glibc 2.0.112.
.SH BUGS
-It is rather unfortunate that Linux revived this spectre from the past.
+It is rather unfortunate that Linux revived this specter from the past.
The BSD man page states:
"This system call will be eliminated when proper system sharing mechanisms
are implemented.
.\" 2004-11-11, mtk
.\" Added waitid(2); added WCONTINUED and WIFCONTINUED()
.\" Added text on SA_NOCLDSTOP
-.\" Updated discussion of SA_NOCLDWAIT to reflect 2.6 behaviour
+.\" Updated discussion of SA_NOCLDWAIT to reflect 2.6 behavior
.\" Much other text rewritten
.\" 2005-05-10, mtk, __W* flags can't be used with waitid()
.\"
argument has changed state.
By default,
.BR waitpid ()
-waits only for terminated children, but this behaviour is modifiable
+waits only for terminated children, but this behavior is modifiable
via the
.I options
argument, as described below.
.I errno
set to
.BR ECHILD .
-(The original POSIX standard left the behaviour of setting
+(The original POSIX standard left the behavior of setting
.B SIGCHLD
to
.B SIG_IGN
using the integer supplied on the command line as the exit status.
The parent process executes a loop that monitors the child using
.BR waitpid (2),
-and uses the W*() macros described above to analyse the wait status value.
+and uses the W*() macros described above to analyze the wait status value.
The following shell session demonstrates the use of the program:
.nf
NaN is a NaN ("not-a-number") that does not raise exceptions
when it is used in arithmetic.
The opposite is a
-.I signalling
+.I signaling
NaN.
See IEC 60559:1989.
may be a pointer to a static buffer, possibly overwritten
by later calls.
.LP
-The behaviour of
+The behavior of
.BR l64a ()
is undefined when
.I value
.\"
.TH ADJTIME 3 2006-05-01 "Linux" "Linux Programmer's Manual"
.SH NAME
-adjtime \- correct the time to synchronise the system clock
+adjtime \- correct the time to synchronize the system clock
.SH SYNOPSIS
.nf
.B #define _BSD_SOURCE
.IR fd .
If
.I aiocbp
-is NULL, all such requests are cancelled.
+is NULL, all such requests are canceled.
Otherwise, only the request
described by the control block pointed to by
.I aiocbp
-is cancelled.
+is canceled.
.LP
-Normal asynchronous notification occurs for cancelled requests.
+Normal asynchronous notification occurs for canceled requests.
The request return status is set to \-1, and the request error status
is set to ECANCELED.
-The control block of requests that cannot be cancelled is not changed.
+The control block of requests that cannot be canceled is not changed.
.LP
If
.I aiocbp
.\" FreeBSD: not those on raw disk devices.
.SH "RETURN VALUE"
This function returns AIO_CANCELED if all requests were successfully
-cancelled.
+canceled.
It returns AIO_NOTCANCELED when at least one of the
-requests specified was not cancelled because it was in progress.
+requests specified was not canceled because it was in progress.
In this case one may check the status of individual requests using
.BR aio_error (3).
This function returns AIO_ALLDONE when all requests had
.SH "RETURN VALUE"
This function returns EINPROGRESS if the request has not been
completed yet.
-It returns ECANCELED if the request was cancelled.
+It returns ECANCELED if the request was canceled.
It returns 0 if the request completed successfully.
Otherwise an error value is returned, the same value that would have
been stored in the
The
.BR alloca ()
function returns a pointer to the beginning of the allocated space.
-If the allocation causes stack overflow, program behaviour is undefined.
+If the allocation causes stack overflow, program behavior is undefined.
.SH "CONFORMING TO"
There is evidence that the
.BR alloca ()
with messy consequences if one has a private version of this function.
.LP
The fact that the code is inlined, means that it is impossible
-to take the address of this function, or to change its behaviour
+to take the address of this function, or to change its behavior
by linking with a different library.
.LP
The inlined code often consists of a single instruction adjusting
.BR asprintf ()
and
.BR vasprintf ()
-are analogues of
+are analogs of
.BR sprintf (3)
and
.BR vsprintf (3),
.SH BUGS
.BR assert ()
is implemented as a macro; if the expression tested has side-effects,
-program behaviour will be different depending on whether
+program behavior will be different depending on whether
.B NDEBUG
is defined.
This may create Heisenbugs which go away when debugging
.BR atof ()
function converts the initial portion of the string
pointed to by \fInptr\fP to double.
-The behaviour is the same as
+The behavior is the same as
.sp
.RS
.B strtod(nptr, (char **) NULL);
function converts the initial portion of the string
pointed to by \fInptr\fP to
.IR int .
-The behaviour is the same as
+The behavior is the same as
.sp
.RS
.B strtol(nptr, (char **) NULL, 10);
.SH "CONFORMING TO"
C99, POSIX.1-2001.
.SH NOTES
-The behaviour of
+The behavior of
.BR btowc ()
depends on the LC_CTYPE category of the
current locale.
when the message catalog is available but does not contain
the specified message.
These two possible error returns seem to be discarded in SUSv2
-in favour of always returning
+in favor of always returning
.IR message .
.SH "SEE ALSO"
.BR catopen (3),
Linux does not include the times of waited-for children in the
value returned by
.BR clock ().
-.\" I have seen this behaviour on Irix 6.3, and the OSF/1, HP/UX, and
+.\" I have seen this behavior on Irix 6.3, and the OSF/1, HP/UX, and
.\" Solaris manual pages say that clock() also does this on those systems.
.\" POSIX.1-2001 doesn't explicitly allow this, nor is there an
.\" explicit prohibition. -- MTK
.BR RTLD_NODELETE " (since glibc 2.2)"
Do not unload the library during
.BR dlclose ().
-Consequently, the library's static variables are not reinitialised
+Consequently, the library's static variables are not reinitialized
if the library is reloaded with
.BR dlopen ()
at a later time.
.BR dprintf ()
and
.BR vdprintf ()
-(as found in the glibc2 library) are exact analogues of
+(as found in the glibc2 library) are exact analogs of
.BR fprintf (3)
and
.BR vfprintf (3),
In either case any further access
(including another call to
.BR fclose ())
-to the stream results in undefined behaviour.
+to the stream results in undefined behavior.
.SH ERRORS
.TP
.B EBADF
.SH "CONFORMING TO"
C99, POSIX.1-2001.
.SH NOTES
-The behaviour of
+The behavior of
.BR fgetwc ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99, POSIX.1-2001.
.SH NOTES
-The behaviour of
+The behavior of
.BR fgetws ()
depends on the LC_CTYPE category of the
current locale.
The result is rounded according to the
rounding mode determined by the value of FLT_ROUNDS.
FLT_ROUNDS indicates the implementation-defined rounding
-behaviour for floating-point addition,
+behavior for floating-point addition,
and has one of the following values:
.IP \-1
The rounding mode is not determinable.
.PP
The
.I flags
-argument modifies the behaviour; it is the bitwise OR of zero or more
+argument modifies the behavior; it is the bitwise OR of zero or more
of the following flags:
.TP
.B FNM_NOESCAPE
.SH "CONFORMING TO"
C99, POSIX.1-2001.
.SH NOTES
-The behaviour of
+The behavior of
.BR fputwc ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99, POSIX.1-2001.
.SH NOTES
-The behaviour of
+The behavior of
.BR fputws ()
depends on the LC_CTYPE category of the
current locale.
but still only 8 bits are used.
Typical usage has an ASCII character
.IR proj_id ,
-that is why the behaviour is said to be undefined when
+that is why the behavior is said to be undefined when
.I proj_id
is zero.
.LP
.PP
If
.I buf
-is NULL, the behaviour of
+is NULL, the behavior of
.BR getcwd ()
is undefined.
.PP
.LP
When
.B %Z
-is given, the value to be returned is initialised to the broken-down time
+is given, the value to be returned is initialized to the broken-down time
corresponding to the current time in the given time zone.
-Otherwise, it is initialised to the broken-down time corresponding to
+Otherwise, it is initialized to the broken-down time corresponding to
the current local time.
.LP
When only the weekday is given, the day is taken to be the first such day
The
.I flags
-argument modifies the behaviour of
+argument modifies the behavior of
.BR getnameinfo (3)
as follows:
.TP
(The
.B \-W
option is reserved by POSIX.2 for implementation extensions.)
-This behaviour is a GNU extension, not available with libraries before
+This behavior is a GNU extension, not available with libraries before
GNU libc 2.
.PP
By default,
.B bash
2.0 to communicate to GNU libc which arguments are the results of
wildcard expansion and so should not be considered as options.
-This behaviour was removed in
+This behavior was removed in
.B bash
version 2.01, but the support remains in GNU libc.
.SH "CONFORMING TO"
has a technical error described in POSIX.2 Interpretation 150.
The GNU
implementation (and probably all other implementations) implements the
-correct behaviour rather than that specified.
+correct behavior rather than that specified.
.SH EXAMPLE
The following trivial example program uses
.BR getopt ()
.RI * valuep
is precisely the "value string" for that suboption.
-If the suboption is recognised, but no value string was found,
+If the suboption is recognized, but no value string was found,
.RI * valuep
is set to NULL.
.SH RETURN VALUE
If the first suboption in
.I optionp
-is recognised,
+is recognized,
.BR getsubopt ()
returns the index of the matching suboption element in
.I tokens .
.BR umask (2)
library call).
.SH "CONFORMING TO"
-This is a vapourware GNU extension.
+This is a vaporware GNU extension.
.SH NOTES
This function is documented but not implemented yet in glibc 2.2.5.
.SH "SEE ALSO"
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR getwchar ()
depends on the LC_CTYPE category of the
current locale.
The parameter
.I flags
is made up of bitwise OR of zero or more the following symbolic
-constants, which modify the of behaviour of
+constants, which modify the of behavior of
.BR glob ():
.TP
.B GLOB_ERR
respectively.
.LP
Elsewhere, on System V-like systems, these functions implement
-software signalling, entirely independent of the classical
+software signaling, entirely independent of the classical
signal and kill functions.
The function
.BR ssignal ()
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswalnum ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswalpha ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
POSIX.1-2001.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswblank ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswcntrl ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswctype ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswdigit ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswgraph ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswlower ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswprint ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswpunct ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswspace ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswupper ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR iswxdigit ()
depends on the LC_CTYPE category of the
current locale.
.BR realloc ().
Otherwise, or if
.BI "free(" "ptr" )
-has already been called before, undefined behaviour occurs.
+has already been called before, undefined behavior occurs.
If
.I ptr
is NULL, no operation is performed.
/* Variables to save original hooks. */
static void *(*old_malloc_hook)(size_t, const void *);
-/* Override initialising hook from the C library. */
+/* Override initializing hook from the C library. */
void (*__malloc_initialize_hook) (void) = my_init_hook;
static void
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR mblen ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR mbrlen ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR mbrtowc ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR mbsinit ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
This function is a GNU extension.
.SH NOTES
-The behaviour of
+The behavior of
.BR mbsnrtowcs ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR mbsrtowcs ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR mbstowcs ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99
.SH NOTES
-The behaviour of
+The behavior of
.BR mbtowc ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
4.3BSD, POSIX.1-2001
.SH NOTES
-The old behaviour (creating a file with mode 0666) may be
-a security risk, especially since other Unix flavours use 0600,
+The old behavior (creating a file with mode 0666) may be
+a security risk, especially since other Unix flavors use 0600,
and somebody might overlook this detail when porting programs.
More generally, the POSIX specification does not say anything
The
.I mq_flags
field contains flags associated with the open message queue description.
-This field is initialised when the queue is created by
+This field is initialized when the queue is created by
.BR mq_open (3).
The only flag that can appear in this field is
.BR O_NONBLOCK .
.IR program_invocation_name ,
with all text up to and including the final slash (/), if any, removed.
-These variables are automatically initialised by the glibc run-time
+These variables are automatically initialized by the glibc run-time
startup code.
.SH "CONFORMING TO"
These variables are GNU extensions, and should not be
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR putwchar ()
depends on the LC_CTYPE category of the
current locale.
This might just be
the seed value to be used by the next call, or it might be something
more elaborate.
-In order to get reproducible behaviour in a threaded
+In order to get reproducible behavior in a threaded
application, this state must be made explicit.
The function
.BR rand_r ()
.B REG_NOTBOL
and
.B REG_NOTEOL
-which cause changes in matching behaviour described below.
+which cause changes in matching behavior described below.
.TP
.B REG_NOTBOL
The match-beginning-of-line operator always fails to match (but see the
.I pointer
argument, which should be a pointer to a
.I "char *"
-variable (this variable does not need to be initialised before the call).
+variable (this variable does not need to be initialized before the call).
The caller should subsequently
.BR free (3)
this buffer when it is no longer required.
.B q
and
.B a
-as well as an additional behaviour of the
+as well as an additional behavior of the
.B L
and
.B l
specifiers.
The latter may be considered to be a bug, as it changes the
-behaviour of specifiers defined in C89.
+behavior of specifiers defined in C89.
.PP
Some combinations of the type modifiers and conversion
specifiers defined by ANSI C do not make sense
(e.g.
.BR "%Ld" ).
-While they may have a well-defined behaviour on Linux, this need not
+While they may have a well-defined behavior on Linux, this need not
to be so on other architectures.
Therefore it usually is better to use
modifiers that are not defined by ANSI C at all, i.e. use
destroys the unnamed semaphore at the address pointed to by
.IR sem .
-Only a semaphore that has been initialised by
+Only a semaphore that has been initialized by
.BR sem_init (3)
should be destroyed using
.BR sem_destroy ().
Destroying a semaphore that other processes or threads are
currently blocked on (in
.BR sem_wait (3))
-produces undefined behaviour.
+produces undefined behavior.
Using a semaphore that has been destroyed produces undefined results,
-until the semaphore has been reinitialised using
+until the semaphore has been reinitialized using
.BR sem_init (3).
.SH RETURN VALUE
.BR sem_destroy ()
or a negative number whose absolute value is the count
of the number of processes and threads currently blocked in
.BR sem_wait (3).
-Linux adopts the former behaviour.
+Linux adopts the former behavior.
.SH RETURN VALUE
.BR sem_getvalue ()
returns 0 on success;
.\"
.TH SEM_INIT 3 2006-03-25 "Linux" "Linux Programmer's Manual"
.SH NAME
-sem_init \- initialise an unnamed semaphore
+sem_init \- initialize an unnamed semaphore
.SH SYNOPSIS
.nf
.B #include <semaphore.h>
.fi
.SH DESCRIPTION
.BR sem_init ()
-initialises the unnamed semaphore at the address pointed to by
+initializes the unnamed semaphore at the address pointed to by
.IR sem .
The
.I value
.BR sem_wait (3),
etc.
-Initialising a semaphore that has already been initialised
-results in undefined behaviour.
+Initializing a semaphore that has already been initialized
+results in undefined behavior.
.SH RETURN VALUE
.BR sem_init ()
returns 0 on success;
.\"
.TH SEM_OPEN 3 2006-03-25 "Linux" "Linux Programmer's Manual"
.SH NAME
-sem_open \- initialise and open a named semaphore
+sem_open \- initialize and open a named semaphore
.SH SYNOPSIS
.nf
.B #include <semaphore.h>
returns 0 on success.
It can return any value on failure, but returns non-zero when
.I mode
-is invalid or the request cannot be honoured.
+is invalid or the request cannot be honored.
It may set
.I errno
on failure.
.\" Modified Fri Feb 14 21:47:50 1997 by Andries Brouwer (aeb@cwi.nl)
.\" Modified 9 Jun 2004, Michael Kerrisk <mtk-manpages@gmx.net>
.\" Changed unsetenv() prototype; added EINVAL error
-.\" Noted non-standard behaviour of setenv() if name contains '='
+.\" Noted non-standard behavior of setenv() if name contains '='
.\" 2005-08-12, mtk, glibc 2.3.4 fixed the "name contains '='" bug
.\"
.TH SETENV 3 2004-05-09 "GNU" "Linux Programmer's Manual"
object can be set using
.BR ftruncate (2).
The newly allocated bytes of a shared memory
-object are automatically initialised to 0.
+object are automatically initialized to 0.
.TP
.B O_EXCL
If
.SH DESCRIPTION
The
.BR siginterrupt ()
-function changes the restart behaviour when
+function changes the restart behavior when
a system call is interrupted by the signal \fIsig\fP.
If the \fIflag\fP
argument is false (0), then system calls will be restarted if interrupted
by the specified signal \fIsig\fP.
-This is the default behaviour in Linux.
+This is the default behavior in Linux.
However, when a new signal handler is specified with the
.BR signal (2)
function, the system call is interrupted by default.
.BR sigmask ()
function constructs and returns a "signal mask" for
.IR signum .
-For example, we can initialise the
+For example, we can initialize the
.I vec.sv_mask
field given to
.BR sigvec ()
is not large enough
(that is, if the programmer was stupid or lazy, and failed to check
the size before copying) then anything might happen.
-Overflowing fixed length strings is a favourite cracker technique.
+Overflowing fixed length strings is a favorite cracker technique.
.SH "SEE ALSO"
.BR bcopy (3),
.BR memccpy (3),
.I modifier
to indicate that an alternative format should be used.
If the alternative format or specification does not exist for
-the current locale, the behaviour will be as if the unmodified
+the current locale, the behavior will be as if the unmodified
conversion specification were used. (SU)
The Single Unix Specification mentions %Ec, %EC, %Ex, %EX,
%Ey, %EY, %Od, %Oe, %OH, %OI, %Om, %OM, %OS, %Ou, %OU, %OV,
The 12-hour clock time (using the locale's AM or PM).
In the POSIX locale equivalent to %I:%M:%S %p.
If \fIt_fmt_ampm\fP is empty in the LC_TIME part of the current locale
-then the behaviour is undefined.
+then the behavior is undefined.
.TP
.B %R
Equivalent to %H:%M.
.IR <stdio.h> )
times.
If it is called more than TMP_MAX times,
-the behaviour is implementation defined.
+the behavior is implementation defined.
.LP
.BR tempnam ()
uses at most the first five bytes from
function generates a different string each time it is called,
up to TMP_MAX times.
If it is called more than TMP_MAX times,
-the behaviour is implementation defined.
+the behavior is implementation defined.
.LP
Although
.BR tmpnam (3)
.PP
If
.I c
-is not an unsigned char value, or EOF, the behaviour of these functions
+is not an unsigned char value, or EOF, the behavior of these functions
is undefined.
.SH "RETURN VALUE"
The value returned is that of the converted letter, or
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR towctrans ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR towlower ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR towupper ()
depends on the LC_CTYPE category of the
current locale.
110 baud).
Thus a typical line was "18\-".
A hang on some line was solved by changing the '1' to a '0',
-signalling init, changing back again, and signalling init again.
+signaling init, changing back again, and signaling init again.
.LP
In Unix V7 the format was changed: here the second character
was the argument to
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR ungetwc ()
depends on the LC_CTYPE category of the
current locale.
.BI "int fputws_unlocked(const wchar_t *" ws ", FILE *" stream );
.fi
.SH DESCRIPTION
-Each of these functions has the same behaviour as its counterpart
+Each of these functions has the same behavior as its counterpart
without the `_unlocked' suffix, except that they do not use locking
(they do not set locks themselves, and do not test for the presence
of locks set by others) and hence are thread-unsafe.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wcrtomb ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
This function is a GNU extension.
.SH NOTES
-The behaviour of
+The behavior of
.BR wcscasecmp ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
This function is a GNU extension.
.SH NOTES
-The behaviour of
+The behavior of
.BR wcsncasecmp ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
This function is a GNU extension.
.SH NOTES
-The behaviour of
+The behavior of
.BR wcsnrtombs ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wcsrtombs ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wcstombs ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
POSIX.1-2001.
.SH NOTES
-The behaviour of
+The behavior of
.BR wcswidth ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wctob ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wctomb ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wctrans ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wctype ()
depends on the LC_CTYPE category of the
current locale.
.BI "int wcwidth(wint_t " c );
.fi
.SH NOTES
-The behaviour of
+The behavior of
.BR wcwidth ()
depends on the LC_CTYPE category of the
current locale.
.SH "CONFORMING TO"
C99.
.SH NOTES
-The behaviour of
+The behavior of
.BR wprintf ()
et al. depends
on the LC_CTYPE category of the
\fIargp\fP = 0 turns sound off.
In either case, control returns immediately.
.IP \fBGIO_CMAP\fP
-Get the current default colour map from kernel.
+Get the current default color map from kernel.
\fIargp\fP points to
a 48-byte array.
(Since 1.3.3.)
.IP \fBPIO_CMAP\fP
-Change the default text-mode colour map.
+Change the default text-mode color map.
\fIargp\fP points to a
48-byte array which contains, in order, the Red, Green, and Blue
-values for the 16 available screen colours: 0 is off, and 255 is full
+values for the 16 available screen colors: 0 is off, and 255 is full
intensity.
-The default colours are, in order: black, dark red, dark
+The default colors are, in order: black, dark red, dark
green, brown, dark blue, dark purple, dark cyan, light grey, dark
grey, bright red, bright green, yellow, bright blue, bright purple,
bright cyan and white. (Since 1.3.3.)
Torvalds.
It was further improved by Michael K.\& Johnson.
The interrupt code was written by Nigel Gamble.
-Alan Cox modularised it.
+Alan Cox modularized it.
LPCAREFUL, LPABORT, LPGETSTATUS were added by Chris Metcalf.
.SH "SEE ALSO"
.BR chmod (1),
1200 *n
.TE
-The first byte of a data packet can be used to synchronisation purposes.
+The first byte of a data packet can be used to synchronization purposes.
.SS "Microsoft protocol"
The \fBMicrosoft\fP protocol uses 1 start bit, 7 data bits, no parity
and one stop bit at the speed of 1200 bits/sec.
.\" sense for LinuxThreads, where each thread had a unique PID,
.\" but doesn't seem to server any purpose with NPTL, where all the
.\" threads in a process share the same PID (as POSIX.1 requires).
-.\" Probably the behaviour is maintained so that applications using
+.\" Probably the behavior is maintained so that applications using
.\" LinuxThreads continue appending the PID (the kernel has no easy
.\" way of telling which threading implementation the userspace
.\" application is using). -- mtk, April 2006
Three different integer values can be specified:
.sp
\fI0\ (default)\fP
-This provides the traditional (pre-Linux 2.6.13) behaviour.
+This provides the traditional (pre-Linux 2.6.13) behavior.
A core dump will not be produced for a process which has
changed credentials (by calling
.BR seteuid (2),
This file
contains three numbers: highwater, lowwater and frequency.
If BSD-style process accounting is enabled these values control
-its behaviour.
+its behavior.
If free space on filesystem where the log lives
goes below lowwater percent accounting suspends.
If free space gets
(This file is only present in Linux 2.4 onwards.)
.TP
.I /proc/sys/kernel/msgmnb
-This file defines a system-wide parameter used to initialise the
+This file defines a system-wide parameter used to initialize the
.I msg_qbytes
setting for subsequently created message queues.
The
software watchdog device driver, the recommended setting is 60.
.TP
.I /proc/sys/kernel/panic_on_oops
-This file (new in Linux 2.5) controls the kernel's behaviour when an oops
+This file (new in Linux 2.5) controls the kernel's behavior when an oops
or BUG is encountered.
If this file contains 0, then the system
tries to continue operation.
.TP
.IR /proc/zoneinfo " (since Linux 2.6.13)"
This file display information about memory zones.
-This is useful for analysing virtual memory behaviour.
+This is useful for analyzing virtual memory behavior.
.\" FIXME more should be said about /proc/zoneinfo
.RE
.RE
.BR getservbyname (3),
and
.BR getservbyport (3).
-However, this behaviour should not be relied on.)
+However, this behavior should not be relied on.)
As a backwards compatibility feature, the slash (/) between the
.I port
Entries which are marked
as permanent are never deleted by the garbage-collector.
The cache can
-be directly manipulated by the use of ioctls and its behaviour can be
+be directly manipulated by the use of ioctls and its behavior can be
tuned by the sysctls defined below.
When there is no positive feedback for an existing mapping after some
-time (see the sysctls below) a neighbour cache entry is considered stale.
+time (see the sysctls below) a neighbor cache entry is considered stale.
Positive feedback can be gotten from a higher layer; for example from
a successful TCP ACK.
Other protocols can signal forward progress
.TP
.B anycast_delay
The maximum number of jiffies to delay before replying to a
-IPv6 neighbour solicitation message.
+IPv6 neighbor solicitation message.
Anycast support is not yet implemented.
Defaults to 1 second.
.TP
Defaults to 0.
.TP
.B base_reachable_time
-Once a neighbour has been found, the entry is considered to be valid
+Once a neighbor has been found, the entry is considered to be valid
for at least a random value between
.IR base_reachable_time "/2 and 3*" base_reachable_time /2.
An entry's validity will be extended if it receives positive feedback
Defaults to 30 seconds.
.TP
.B delay_first_probe_time
-Delay before first probe after it has been decided that a neighbour
+Delay before first probe after it has been decided that a neighbor
is stale.
Defaults to 5 seconds.
.TP
.B gc_interval
-How frequently the garbage collector for neighbour entries
+How frequently the garbage collector for neighbor entries
should attempt to run.
Defaults to 30 seconds.
.TP
.B gc_stale_time
-Determines how often to check for stale neighbour entries.
-When a neighbour entry is considered stale it is resolved again before
+Determines how often to check for stale neighbor entries.
+When a neighbor entry is considered stale it is resolved again before
sending data to it.
Defaults to 60 seconds.
.TP
.PP
RFC\ 826 for a description of ARP.
.br
-RFC\ 2461 for a description of IPv6 neighbour discovery and the base
+RFC\ 2461 for a description of IPv6 neighbor discovery and the base
algorithms used.
.LP
Linux 2.2+ IPv4 ARP uses the IPv6 algorithms when applicable.
Specifying a one indicates parity checking is enabled,
and a zero disables parity checking.
Again, not all adapters will support selection of parity
-behaviour as a boot argument.
+behavior as a boot argument.
.SS "`max_scsi_luns=...'"
A SCSI device can have a number of `sub-devices' contained within
itself.
.SS "XT Disk Driver Options (`xd=')"
If you are unfortunate enough to be using one of these old 8 bit cards
that move data at a whopping 125kB/s then here is the scoop.
-If the card is not recognised, you will have to use a boot arg of the form:
+If the card is not recognized, you will have to use a boot arg of the form:
.IP
xd=type,irq,iobase,dma_chan
.LP
cmos for those drives.
.SS "floppy=unexpected_interrupts"
Print a warning message when an unexpected interrupt is received
-(default behaviour)
+(default behavior)
.SS "floppy=no_unexpected_interrupts or floppy=L40SX"
Don't print a message when an unexpected interrupt is received.
This is needed on IBM L40SX laptops in certain video modes.
and
.BR unsetenv (3).
-Note that the behaviour of many programs and library routines is
+Note that the behavior of many programs and library routines is
influenced by the presence or value of certain environment variables.
A random collection:
.LP
.LP
.BR LD_LIBRARY_PATH ", " LD_PRELOAD
and other LD_* variables influence
-the behaviour of the dynamic loader/linker.
+the behavior of the dynamic loader/linker.
.LP
.B POSIXLY_CORRECT
makes certain programs and library routines follow
the prescriptions of POSIX.
.LP
-The behaviour of
+The behavior of
.BR malloc (3)
is influenced by MALLOC_* variables.
.LP
.B Q9
Do I need to continuously read/write an fd until EAGAIN when using the
.B EPOLLET
-flag ( Edge Triggered behaviour ) ?
+flag ( Edge Triggered behavior ) ?
.TP
.B A9
No you don't.
.B _FORTIFY_SOURCE
is set to 1, with compiler optimization level 1
.RI ( "gcc -O1" )
-and above, checks that shouldn't change the behaviour of
+and above, checks that shouldn't change the behavior of
conforming programs are performed.
With
.B _FORTIFY_SOURCE
Under Linux, opening a FIFO for read and write will succeed
both in blocking and non-blocking mode.
POSIX leaves this
-behaviour undefined.
+behavior undefined.
This can be used to open a FIFO for
writing while there are no readers available.
A process
Futex operation is entirely userspace for the non-contended case.
The kernel is only involved to arbitrate the contended case.
As any sane design will strive for non-contention,
-futexes are also optimised for this situation.
+futexes are also optimized for this situation.
.PP
In its bare form, a futex is an aligned integer which is
only touched by atomic assembler instructions.
matching pathnames is empty.
With
.I bash
-one can force the classical behaviour by setting
+one can force the classical behavior by setting
.IR allow_null_glob_expansion=true .
(Similar problems occur elsewhere.
structure is thus
.IR "sizeof(inotify_event)+len" .
-The behaviour when the buffer given to
+The behavior when the buffer given to
.BR read (2)
is too small to return information about the next event depends
on the kernel version: in kernels before 2.6.21,
Linux sends
.B IPTOS_LOWDELAY
datagrams first by default,
-but the exact behaviour depends on the configured queueing discipline.
+but the exact behavior depends on the configured queueing discipline.
.\" FIXME elaborate on this
Some high priority levels may require superuser privileges (the
.B CAP_NET_ADMIN
function, it is possible to set one of these to the desired locale:
.TP
.B LC_COLLATE
-This is used to change the behaviour of the functions
+This is used to change the behavior of the functions
.BR strcoll (3)
and
.BR strxfrm (3),
the German sharp s is sorted as "ss".
.TP
.B LC_CTYPE
-This changes the behaviour of the character handling and
+This changes the behavior of the character handling and
classification functions, such as
.BR isupper (3)
and
function.
.TP
.B LC_TIME
-changes the behaviour of the
+changes the behavior of the
.BR strftime (3)
function to display the current time in a locally acceptable form; for
example, most of Europe uses a 24\-hour clock versus the
.TP
*
Where possible and appropriate, example programs should allow
-experimentation, by varying their behaviour based on inputs
+experimentation, by varying their behavior based on inputs
(ideally from command-line arguments, or alternatively, via
input read by the program).
.TP
.B NETLINK_ROUTE
Receives routing and link updates and may be used to modify the routing
tables (both IPv4 and IPv6), IP addresses, link parameters,
-neighbour setups, queueing disciplines, traffic classes and
+neighbor setups, queueing disciplines, traffic classes and
packet classifiers (see
.BR rtnetlink (7)).
.TP
.B ENOBUFS
error returned by
.BR recvmsg (2))
-and resynchronise.
+and resynchronize.
.SS Address Formats
The
.I sockaddr_nl
posixoptions \- optional parts of the POSIX standard
.SH DESCRIPTION
The POSIX standard (the information below is from POSIX.1-2001)
-describes a set of behaviours and interfaces for a compliant system.
+describes a set of behavior and interfaces for a compliant system.
However, many interfaces are optional and there are feature test macros
to test the availability of interfaces at compile time, and functions
.BR sysconf (3),
Both threading implementations employ the Linux
.BR clone (2)
system call.
-In NPTL, thread synchronisation primitives (mutexes,
+In NPTL, thread synchronization primitives (mutexes,
thread joining, etc.) are implemented using the Linux
.BR futex (2)
system call.
and this API should be employed in all new programs that use
pseudo-terminals.
-Linux provides both BSD-style and (standardised) System V-style
+Linux provides both BSD-style and (standardized) System V-style
pseudo-terminals.
System V-style terminals are commonly called Unix 98 pseudo-terminals
on Linux systems.
.IR /dev/ptmx ;
see
.BR pts (4).)
-After performing any program-specific initialisations,
+After performing any program-specific initializations,
changing the ownership and permissions of the slave device using
.BR grantpt (3),
and unlocking the slave using
It is used within the kernel to communicate between
various subsystems, though this usage is not documented here, and for
communication with user-space programs.
-Network routes, ip addresses, link parameters, neighbour setups, queueing
+Network routes, ip addresses, link parameters, neighbor setups, queueing
disciplines, traffic classes and packet classifiers may all be controlled
through
.B NETLINK_ROUTE
.B Fill these values in!
.TP
.BR RTM_NEWNEIGH ", " RTM_DELNEIGH ", " RTM_GETNEIGH
-Add, remove or receive information about a neighbour table
+Add, remove or receive information about a neighbor table
entry (e.g. an ARP entry).
The message contains an
.B ndmsg
tab(:);
l l.
NDA_UNSPEC:unknown type
-NDA_DST:a neighbour cache n/w layer destination address
-NDA_LLADDR:a neighbour cache link layer address
+NDA_DST:a neighbor cache n/w layer destination address
+NDA_LLADDR:a neighbor cache link layer address
NDA_CACHEINFO:cache statistics.
.TE
.SH NAME
sem_overview \- Overview of POSIX semaphores
.SH DESCRIPTION
-POSIX semaphores allow processes and threads to synchronise their actions.
+POSIX semaphores allow processes and threads to synchronize their actions.
A semaphore is an integer whose value is never allowed to fall below zero.
Two operations can be performed on semaphores:
or a POSIX shared memory object built created using
.BR shm_open (3)).
-Before being used, an unnamed semaphore must be initialised using
+Before being used, an unnamed semaphore must be initialized using
.BR sem_init (3).
It can then be operated on using
.BR sem_post (3)
or (less portably)
.BR signal (2).
Using these system calls, a process can elect one of the
-following behaviours to occur on delivery of the signal:
+following behavior to occur on delivery of the signal:
perform the default action; ignore the signal;
or catch the signal with a
.IR "signal handler" ,
SIGXFSZ 25,25,31 Core File size limit exceeded (4.2BSD)
.TE
-Up to and including Linux 2.2, the default behaviour for
+Up to and including Linux 2.2, the default behavior for
.BR SIGSYS ", " SIGXCPU ", " SIGXFSZ ", "
and (on architectures other than SPARC and MIPS)
.B SIGBUS
.RB ( SO_SNDLOWAT )
or the user on receiving
.RB ( SO_RCVLOWAT ).
-These two values are initialised to 1.
+These two values are initialized to 1.
.B SO_SNDLOWAT
is not changeable on Linux
.RB ( setsockopt
Informative text on the other parts of the standard.
.sp
POSIX.1-2001 is aligned with C99, so that all of the
-library functions standardised in C99 are also
-standardised in POSIX.1-1001.
+library functions standardized in C99 are also
+standardized in POSIX.1-1001.
.sp
Two Technical Corrigenda (minor fixes and improvements)
of the original 2001 standard have occurred:
.am \fBautomake\fP(1) input file
.arc \fBarc\fP(1) archive
.arj \fBarj\fP(1) archive
- .asc PGP ASCII-armoured data
+ .asc PGP ASCII-armored data
.asm (GNU) assembler source file
.au Audio sound file
.aux LaTeX auxiliary file
short.
.TP
.BR tcp_rfc1337 " (Boolean; default: disabled)"
-Enable TCP behaviour conformant with RFC\ 1337.
+Enable TCP behavior conformant with RFC\ 1337.
When disabled,
if a RST is received in TIME_WAIT state, we close
the socket immediately without waiting for the end
operations that existed in System V.
(This was done because
.BR ioctl (2)
-was unstandardised, and its variadic third argument
+was unstandardized, and its variadic third argument
does not allow argument type checking.)
If you're looking for page called "termio", then you can probably
received from the network.
You may get an error for an earlier packet
that was sent on the same socket.
-This behaviour differs from many other BSD socket implementations
+This behavior differs from many other BSD socket implementations
which don't pass any errors unless the socket is connected.
-Linux's behaviour is mandated by
+Linux's behavior is mandated by
.BR RFC\ 1122 .
For compatibility with legacy code in Linux 2.0 and 2.2
but the implementation details differ.)
.SH NOTES
In the Linux implementation, sockets which are visible in the
-filesystem honour the permissions of the directory they are in.
+filesystem honor the permissions of the directory they are in.
Their owner, group and their permissions can be changed.
Creation of a new socket will fail if the process does not have write and
search (execute) permission on the directory the socket is created in.
.SH DESCRIPTION
X25 sockets provide an interface to the X.25 packet layer protocol.
This allows applications to
-communicate over a public X.25 data network as standardised by
+communicate over a public X.25 data network as standardized by
International Telecommunication Union's recommendation X.25
(X.25 DTE-DCE mode).
X25 sockets can also be used for communication
.B ld-linux.so*
handles ELF (\fI/lib/ld-linux.so.1\fP for libc5, \fI/lib/ld-linux.so.2\fP
for glibc2), which everybody has been using for years now.
-Otherwise both have the same behaviour, and use the same
+Otherwise both have the same behavior, and use the same
support files and programs
.BR ldd (1),
.BR ldconfig (8)
.TP
.B LD_DYNAMIC_WEAK
(glibc since 2.1.91)
-Allow weak symbols to be overridden (reverting to old glibc behaviour).
+Allow weak symbols to be overridden (reverting to old glibc behavior).
.TP
.B LD_KEEPDIR
(a.out only)(libc5)
projects / thirdparty / man-pages.git / commitdiff
