.\" Copyright (c) 1991, 1992, 1993
.\" The Regents of the University of California. All rights reserved.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)termios.4 8.4 (Berkeley) 4/19/94
.Nd general terminal line discipline
This describes a general terminal line discipline that is
supported on tty asynchronous communication ports.
.Ss Opening a Terminal Device File
When a terminal file is opened, it normally causes the process to wait
until a connection is established. For most hardware, the presence
of a connection is indicated by the assertion of the hardware
If the termios structure associated with the terminal file has the
flag set in the cflag, or if the
call, then the open will succeed even without
a connection being present.
In practice, applications
seldom open these files; they are opened by special programs, such
an application's standard input, output, and error files.
.Ss Job Control in a Nutshell
Every process is associated with a particular process group and session.
The grouping is hierarchical: every member of a particular process group is a
member of the same session. This structuring is used in managing groups
of related processes for purposes of
ability from the keyboard (or from program control) to simultaneously
a complex command (a command composed of one or more related
processes). The grouping into process groups allows delivering
of signals that stop or start the group as a whole, along with
arbitrating which process group has access to the single controlling
terminal. The grouping at a higher layer into sessions is to restrict
the job control related signals and system calls to within processes
resulting from a particular instance of a "login". Typically, a session
is created when a user logs in, and the login terminal is setup
to be the controlling terminal; all processes spawned from that
login shell are in the same session, and inherit the controlling
operating interactively (that is, reading commands from a terminal)
normally groups related processes together by placing them into the
same process group. A set of processes in the same process group
is collectively referred to as a "job". When the foreground process
group of the terminal is the same as the process group of a particular
job, that job is said to be in the "foreground". When the process
group of the terminal is different than the process group of
a job (but is still the controlling terminal), that job is said
to be in the "background". Normally the
shell reads a command and starts the job that implements that
command. If the command is to be started in the foreground (typical), it
sets the process group of the terminal to the process group
of the started job, waits for the job to complete, and then
sets the process group of the terminal back to its own process
group (it puts itself into the foreground). If the job is to
be started in the background (as denoted by the shell operator "&"),
it never changes the process group of the terminal and doesn't
wait for the job to complete (that is, it immediately attempts to read the next
command). If the job is started in the foreground, the user may
which generates the terminal stop signal
and has the affect of stopping the entire job.
The shell will notice that the job stopped, and will resume running after
placing itself in the foreground.
The shell also has commands for placing stopped jobs in the background,
and for placing stopped or background jobs into the foreground.
.Ss Orphaned Process Groups
An orphaned process group is a process group that has no process
whose parent is in a different process group, yet is in the same
session. Conceptually it means a process group that doesn't have
a parent that could do anything if it were to be stopped. For example,
the initial login shell is typically in an orphaned process group.
Orphaned process groups are immune to keyboard generated stop
signals and job control signals resulting from reads or writes to the
.Ss The Controlling Terminal
A terminal may belong to a process as its controlling terminal. Each
process of a session that has a controlling terminal has the same
controlling terminal. A terminal may be the controlling terminal for at
most one session. The controlling terminal for a session is allocated by
the session leader by issuing the
ioctl. A controlling terminal
is never acquired by merely opening a terminal device file.
When a controlling terminal becomes
associated with a session, its foreground process group is set to
the process group of the session leader.
The controlling terminal is inherited by a child process during a
function call. A process relinquishes its controlling terminal when it
creates a new session with the
function; other processes
remaining in the old session that had this terminal as their controlling
terminal continue to have it.
A process does not relinquish its
controlling terminal simply by closing all of its file descriptors
associated with the controlling terminal if other processes continue to
When a controlling process terminates, the controlling terminal is
disassociated from the current session, allowing it to be acquired by a
new session leader. Subsequent access to the terminal by other processes
in the earlier session will be denied, with attempts to access the
terminal treated as if modem disconnect had been sensed.
.Ss Terminal Access Control
If a process is in the foreground process group of its controlling
terminal, read operations are allowed.
Any attempts by a process
in a background process group to read from its controlling terminal
following special cases apply: If the reading process is ignoring or
.Dv SIGTTIN signal, or if the process group of the reading
signal is sent. The default action of the
process to which it is sent.
If a process is in the foreground process group of its controlling
terminal, write operations are allowed.
Attempts by a process in a background process group to write to its
controlling terminal will cause the process group to be sent a
signal unless one of the following special cases apply: If
is set and the process is ignoring or blocking the
signal, the process is allowed to write to the terminal and the
is set, and the process group of
the writing process is orphaned, and the writing process is not ignoring
Certain calls that set terminal parameters are treated in the same
fashion as write, except that
is ignored; that is, the effect is
identical to that of terminal writes when
.Ss Input Processing and Reading Data
A terminal device associated with a terminal device file may operate in
full-duplex mode, so that data may arrive even while output is occurring.
Each terminal device file has associated with it an input queue, into
which incoming data is stored by the system before being read by a
process. The system imposes a limit,
.Pf \&{ Dv MAX_INPUT Ns \&} ,
bytes that may be stored in the input queue. The behavior of the system
when this limit is exceeded depends on the setting of the
If this flag is set, the terminal
character each time a character is received
while the input queue is full. Otherwise, the input queue is flushed
upon receiving the character.
Two general kinds of input processing are available, determined by
whether the terminal device file is in canonical mode or noncanonical
input characters are processed according to the
fields. Such processing can include echoing, which
in general means transmitting input characters immediately back to the
terminal when they are received from the terminal. This is useful for
terminals that can operate in full-duplex mode.
The manner in which data is provided to a process reading from a terminal
device file is dependent on whether the terminal device file is in
canonical or noncanonical mode.
Another dependency is whether the
flag is clear, then the read request is
blocked until data is available or a signal has been received. If the
flag is set, then the read request is completed, without
blocking, in one of three ways:
If there is enough data available to satisfy the entire request,
and the read completes successfully the number of
If there is not enough data available to satisfy the entire
request, and the read completes successfully, having read as
much data as possible, the number of bytes read is returned.
If there is no data available, the read returns -1, with
When data is available depends on whether the input processing mode is
canonical or noncanonical.
.Ss Canonical Mode Input Processing
In canonical mode input processing, terminal input is processed in units
of lines. A line is delimited by a newline
character, an end-of-file
character, or an end-of-line
This means that a read request will
not return until an entire line has been typed, or a signal has been
received. Also, no matter how many bytes are requested in the read call,
at most one line is returned. It is not, however, necessary to
read a whole line at once; any number of bytes, even one, may be
requested in a read without losing information.
.Pf \&{ Dv MAX_CANON Ns \&}
number of bytes in a line.
The behavior of the system when this limit is
exceeded is the same as when the input queue limit
.Pf \&{ Dv MAX_INPUT Ns \&} ,
Erase and kill processing occur when either of two special characters,
.Sx "Special Characters section" ) ,
This processing affects data in the input queue that has not yet been
character. This un-delimited
data makes up the current line. The
character deletes the last
character in the current line, if there is any. The
deletes all data in the current line, if there is any. The
characters have no effect if there is no data in the current line.
characters themselves are not placed in the input
.Ss Noncanonical Mode Input Processing
In noncanonical mode input processing, input bytes are not assembled into
lines, and erase and kill processing does not occur. The values of the
array are used to determine how to
process the bytes received.
represents the minimum number of bytes that should be received when
function successfully returns.
granularity that is used to time out bursty and short term data
.Dv \&{ Dv MAX_INPUT Ns \&} ,
request is undefined. The four possible values for
their interactions are described below.
.Ss "Case A: MIN > 0, TIME > 0"
serves as an inter-byte timer and is activated after
the first byte is received. Since it is an inter-byte timer, it is reset
after a byte is received. The interaction between
follows: as soon as one byte is received, the inter-byte timer is
bytes are received before the inter-byte timer expires
(remember that the timer is reset upon receipt of each byte), the read is
satisfied. If the timer expires before
characters received to that point are returned to the user. Note that if
expires at least one byte is returned because the timer would
not have been enabled unless a byte was received. In this case
> 0) the read blocks until the
activated by the receipt of the first byte, or a signal is received. If
data is in the buffer at the time of the read(), the result is as
if data had been received immediately after the read().
.Ss "Case B: MIN > 0, TIME = 0"
In this case, since the value of
is zero, the timer plays no role
is significant. A pending read is not satisfied until
bytes are received (i.e., the pending read blocks until
are received), or a signal is received. A program that uses this case to
read record-based terminal
may block indefinitely in the read
.Ss "Case C: MIN = 0, TIME > 0"
no longer represents an inter-byte
timer. It now serves as a read timer that is activated as soon as the
read function is processed. A read is satisfied as soon as a single
byte is received or the read timer expires. Note that in this case if
the timer expires, no bytes are returned. If the timer does not
expire, the only way the read can be satisfied is if a byte is received.
In this case the read will not block indefinitely waiting for a byte; if
no byte is received within
seconds after the read is initiated,
the read returns a value of zero, having read no data. If data is
in the buffer at the time of the read, the timer is started as if
data had been received immediately after the read.
.Ss Case D: MIN = 0, TIME = 0
The minimum of either the number of bytes requested or the number of
bytes currently available is returned without waiting for more
bytes to be input. If no characters are available, read returns a
value of zero, having read no data.
.Ss Writing Data and Output Processing
When a process writes one or more bytes to a terminal device file, they
are processed according to the
implementation may provide a buffering mechanism; as such, when a call to
write() completes, all of the bytes written have been scheduled for
transmission to the device, but the transmission will not necessarily
.\" See also .Sx "6.4.2" for the effects of
Certain characters have special functions on input or output or both.
These functions are summarized as follows:
Special character on input and is recognized if the
section) is enabled. Generates a
signal which is sent to all processes in the foreground
process group for which the terminal is the controlling
discarded when processed.
Special character on input and is recognized if the
flag is enabled. Generates a
sent to all processes in the foreground process group
for which the terminal is the controlling terminal. If
character is discarded when
Special character on input and is recognized if the
flag is set. Erases the last character in the
.Sx "Canonical Mode Input Processing" .
the start of a line, as delimited by an
discarded when processed.
Special character on input and is recognized if the
flag is set. Deletes the entire line, as
character is discarded when processed.
Special character on input and is recognized if the
flag is set. When received, all the bytes
waiting to be read are immediately passed to the
process, without waiting for a newline, and the
is discarded. Thus, if there are no bytes waiting (that
occurred at the beginning of a line), a byte
count of zero is returned from the read(),
representing an end-of-file indication. If
character is discarded when processed.
Special character on input and is recognized if the
flag is set. It is the line delimiter
Special character on input and is recognized if the
flag is set. Is an additional line delimiter,
flag is enabled, receipt of the
signal to be sent to all processes in the
foreground process group for which the terminal is the
controlling terminal, and the
discarded when processed.
Special character on both input and output and is
control) flag is set. Can be used to temporarily
suspend output. It is useful with fast terminals to
prevent output from disappearing before it can be read.
character is discarded when
Special character on both input and output and is
control) flag is set. Can be used to resume output that
character is discarded when processed.
Special character on input and is recognized if the
is not set, this character is translated into a
The following special characters are extensions defined by this
system and are not a part of 1003.1 termios.
character. Same function as
Special character on input and is recognized if the
flag is set. Erases the last word in the current
line according to one of two algorithms. If the
flag is not set, first any preceding whitespace is
erased, and then the maximal sequence of non-whitespace
is set, first any preceding
whitespace is erased, and then the maximal sequence
of alphabetic/underscores or non alphabetic/underscores.
As a special case in this second algorithm, the first previous
non-whitespace character is skipped in determining
whether the preceding word is a sequence of
alphabetic/undercores. This sounds confusing but turns
out to be quite practical.
Special character on input and is recognized if the
flag is set. Causes the current input edit line
Has similar actions to the
signal is delivered when one of the processes
in the foreground process group issues a read() to the
Special character on input and is recognized if the
flag is set. Receipt of this character causes the next
character to be taken literally.
Special character on input and is recognized if the
flag is set. Receipt of this character toggles the flushing
Special character on input and is recognized if the
flag is set. Receipt of this character causes a
signal to be sent to the foreground process group of the
causes the kernel to write a status message to the terminal
that displays the current load average, the name of the
command in the foreground, its process ID, the symbolic
wait channel, the number of user and system seconds used,
the percentage of cpu the process is getting, and the resident
characters cannot be changed.
The values for all the remaining characters can be set and are
described later in the document under
Special Control Characters.
character functions associated with changeable special control characters
can be disabled individually by setting their value to
.Sx "Special Control Characters" .
If two or more special characters have the same value, the function
performed when that character is received is undefined.
If a modem disconnect is detected by the terminal interface for a
controlling terminal, and if
signal is sent to the controlling
process associated with the terminal. Unless other arrangements have
been made, this causes the controlling process to terminate.
Any subsequent call to the read() function returns the value zero,
indicating end of file. Thus, processes that read a terminal
file and test for end-of-file can terminate appropriately after a
.\" condition specified in 6.1.1.4 that applies
.\" when the implementation supports job control also exists, it is
.\" unspecified whether the
subsequent write() to the terminal device returns -1, with
until the device is closed.
.Sh General Terminal Interface
.Ss Closing a Terminal Device File
The last process to close a terminal device file causes any output
to be sent to the device and any input to be discarded. Then, if
is set in the control modes, and the communications port supports a
disconnect function, the terminal device performs a disconnect.
.Ss Parameters That Can Be Set
Routines that need to control certain terminal
do so by using the termios structure as defined in the header
This structure contains minimally four scalar elements of bit flags
and one array of special characters. The scalar flag elements are
The character array is named
terminal input control, and are composed of
.Bl -tag -width IMAXBEL -offset indent -compact
/* ignore BREAK condition */
/* map BREAK to SIGINTR */
/* ignore (discard) parity errors */
/* mark parity and framing errors */
/* enable checking of parity errors */
/* strip 8th bit off chars */
/* map CR to NL (ala CRMOD) */
/* enable output flow control */
/* enable input flow control */
/* any char will restart after stop */
/* ring bell on input queue full */
In the context of asynchronous serial data transmission, a break
condition is defined as a sequence of zero-valued bits that continues for
more than the time to send one byte. The entire sequence of zero-valued
bits is interpreted as a single break condition, even if it continues for
a time equivalent to more than one byte. In contexts other than
asynchronous serial data transmission the definition of a break condition
is implementation defined.
is set, a break condition detected on input is ignored, that
is, not put on the input queue and therefore not read by any process. If
is set, the break condition flushes the
input and output queues and if the terminal is the controlling terminal
of a foreground process group, the break condition generates a
signal to that foreground process group. If neither
is set, a break condition is read as a single
is set, a byte with a framing or parity error (other than
is not set, a byte with a framing or parity
error (other than break) is given to the application as the
flag preceding each sequence and X is the data of the character received
in error. To avoid ambiguity in this case, if
is given to the application as
is set, a framing or parity error (other than
break) is given to the application as a single character
is set, input parity checking is enabled. If
input parity checking is disabled, allowing output parity generation
without input parity errors. Note that whether input parity checking is
enabled or disabled is independent of whether parity detection is enabled
If parity detection is enabled but input
parity checking is disabled, the hardware to which the terminal is
connected recognizes the parity bit, but the terminal special file
does not check whether this bit is set correctly or not.
is set, valid input bytes are first stripped to seven bits,
otherwise all eight bits are processed.
character is translated into a
character is ignored (not
is set, start/stop output control is enabled. A received
character suspends output and a received
is also set, then any character may
read, but merely perform flow control functions. When
is set, start/stop input control is enabled. The system shall
characters, which are intended to cause the
terminal device to stop transmitting data, as needed to prevent the input
queue from overflowing and causing the undefined behavior described in
.Sx "Input Processing and Reading Data" ,
and shall transmit one or more
intended to cause the terminal device to resume transmitting data, as
soon as the device can continue transmitting data without risk of
overflowing the input queue. The precise conditions under which
characters are transmitted are implementation defined.
is set and the input queue is full, subsequent input shall cause an
character to be transmitted to the
The initial input control value after open() is implementation defined.
field describe the basic terminal output control,
and are composed of the following masks:
.Bl -tag -width OXTABS -offset indent -compact
/* enable following output processing */
/* expand tabs to spaces */
is set, the remaining flag masks are interpreted as follows;
otherwise characters are transmitted without change.
is set, newlines are translated to carriage return, linefeeds.
is set, tabs are expanded to the appropriate number of
spaces (assuming 8 column tab stops).
terminal hardware control, and are composed of the
specified are supported by all hardware.
.Bl -tag -width CRTSXIFLOW -offset indent -compact
/* character size mask */
/* odd parity, else even */
/* hang up on last close */
/* ignore modem status lines */
flow control of output */
/* RTS flow control of input */
/* flow control output via Carrier */
bits specify the byte size in bits for both transmission and
This size does not include the parity bit, if any. If
is set, two stop bits are used, otherwise one stop bit. For example, at
110 baud, two stop bits are normally used.
is set, the receiver is enabled. Otherwise, no character is
Not all hardware supports this bit. In fact, this flag
is pretty silly and if it were not part of the
is set, parity generation and detection are enabled and a parity
bit is added to each character. If parity is enabled,
odd parity if set, otherwise even parity is used.
is set, the modem control lines for the port are lowered
when the last process with the port open closes the port or the process
terminates. The modem connection is broken.
is set, a connection does not depend on the state of the modem
is clear, the modem status lines are
Under normal circumstances, a call to the open() function waits for
the modem connection to complete. However, if the
has been set, the open() function returns
immediately without waiting for the connection.
flag is currently unused.
is set then output flow control is controlled by the state
If the object for which the control modes are set is not an asynchronous
serial connection, some of the modes may be ignored; for example, if an
attempt is made to set the baud rate on a network connection to a
terminal on another host, the baud rate may or may not be set on the
connection between that terminal and the machine it is directly connected
field describe the control of
various functions, and are composed of the following
.Bl -tag -width NOKERNINFO -offset indent -compact
/* visual erase for line kill */
/* visually erase chars */
/* visual erase mode for hardcopy */
/* echo control chars as ^(Char) */
/* canonicalize input lines */
/* external processing */
/* stop background jobs from output */
/* output being flushed (state) */
/* XXX retype pending input (state) */
/* don't flush after interrupt */
is set, input characters are echoed back to the terminal. If
is not set, input characters are not echoed.
character causes the terminal
to erase the last character in the current line from the display, if
possible. If there is no character to erase, an implementation may echo
an indication that this was the case or do nothing.
the current line to be discarded and the system echoes the
the current line to be discarded and the system causes
to erase the line from the display.
are set, the system assumes
that the display is a printing device and prints a
backslash and the erased characters when processing
characters, followed by a forward slash.
is set, the system echoes control characters
in a visible fashion using a caret followed by the control character.
is set, the system uses an alternative algorithm
for determining what constitutes a word when processing
is set, canonical processing is enabled. This enables the
erase and kill edit functions, and the assembly of input characters into
.Sx "Canonical Mode Input Processing" .
is not set, read requests are satisfied directly from the input
queue. A read is not satisfied until at least
received or the timeout value
expired between bytes. The time value
represents tenths of seconds. See
.Sx "Noncanonical Mode Input Processing"
is set, each input character is checked against the special
(job control only). If an input
character matches one of these control characters, the function
associated with that character is performed. If
checking is done. Thus these special input functions are possible only
is set, implementation-defined functions are recognized
is implementation defined.
implementation-defined functions are not recognized, and the
corresponding input characters are not processed as described for
is set, the normal flush of the input and output queues
is sent to the process group of a process that tries to write to
its controlling terminal if it is not in the foreground process group for
that terminal. This signal, by default, stops the members of the process
group. Otherwise, the output generated by that process is output to the
current output stream. Processes that are blocking or ignoring
signals are excepted and allowed to produce output and the
is set, the kernel does not produce a status message
.Ss Special Control Characters
The special control characters values are defined by the array
This table lists the array index, the corresponding special character,
and the system default value. For an accurate list of
the system defaults, consult the header file
.Bl -column "Index Name" "Special Character" -offset indent -compact
.It Em "Index Name Special Character Default Value"
.It Dv VEOF Ta EOF Ta \&^D
.It Dv VEOL Ta EOL Ta _POSIX_VDISABLE
.It Dv VEOL2 Ta EOL2 Ta _POSIX_VDISABLE
.It Dv VERASE Ta ERASE Ta \&^? Ql \&\e177
.It Dv VWERASE Ta WERASE Ta \&^W
.It Dv VKILL Ta KILL Ta \&^U
.It Dv VREPRINT Ta REPRINT Ta \&^R
.It Dv VINTR Ta INTR Ta \&^C
.It Dv VQUIT Ta QUIT Ta \&^\e\e Ql \&\e34
.It Dv VSUSP Ta SUSP Ta \&^Z
.It Dv VDSUSP Ta DSUSP Ta \&^Y
.It Dv VSTART Ta START Ta \&^Q
.It Dv VSTOP Ta STOP Ta \&^S
.It Dv VLNEXT Ta LNEXT Ta \&^V
.It Dv VDISCARD Ta DISCARD Ta \&^O
.It Dv VMIN Ta --- Ta \&1
.It Dv VTIME Ta --- Ta \&0
.It Dv VSTATUS Ta STATUS Ta \&^T
value of one of the changeable special control characters (see
.Sx "Special Characters" )
that function is disabled; that is, no input
data is recognized as the disabled special character.
has no special meaning for the
The initial values of the flags and control characters
after open() is set according to
.Aq Pa sys/ttydefaults.h .