git.saurik.com Git - apple/system_cmds.git/blame_incremental

... / ...

Commit	Line	Data
	1	.\" Copyright (c) 1985, 1991, 1993
	2	.\" The Regents of the University of California. All rights reserved.
	3	.\"
	4	.\" Redistribution and use in source and binary forms, with or without
	5	.\" modification, are permitted provided that the following conditions
	6	.\" are met:
	7	.\" 1. Redistributions of source code must retain the above copyright
	8	.\" notice, this list of conditions and the following disclaimer.
	9	.\" 2. Redistributions in binary form must reproduce the above copyright
	10	.\" notice, this list of conditions and the following disclaimer in the
	11	.\" documentation and/or other materials provided with the distribution.
	12	.\" 3. All advertising materials mentioning features or use of this software
	13	.\" must display the following acknowledgement:
	14	.\" This product includes software developed by the University of
	15	.\" California, Berkeley and its contributors.
	16	.\" 4. Neither the name of the University nor the names of its contributors
	17	.\" may be used to endorse or promote products derived from this software
	18	.\" without specific prior written permission.
	19	.\"
	20	.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
	21	.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
	22	.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
	23	.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
	24	.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
	25	.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
	26	.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
	27	.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
	28	.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
	29	.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
	30	.\" SUCH DAMAGE.
	31	.\"
	32	.\" from: @(#)ttys.5 8.1 (Berkeley) 6/4/93
	33	.\" $Id: ttys.5,v 1.1.1.1 1999/05/02 04:21:29 wsanchez Exp $
	34	.\"
	35	.Dd June 4, 1993
	36	.Dt TTYS 5
	37	.Os
	38	.Sh NAME
	39	.Nm ttys
	40	.Nd terminal initialization information
	41	.Sh DESCRIPTION
	42	The file
	43	.Nm ttys
	44	contains information that is used by various routines to initialize
	45	and control the use of terminal special files.
	46	This information is read with the
	47	.Xr getttyent 3
	48	library routines.
	49	There is one line in the
	50	.Nm ttys
	51	file per special device file.
	52	Fields are separated by tabs and/or spaces.
	53	Fields comprised of more than one word should be enclosed in double
	54	quotes (``"'').
	55	Blank lines and comments may appear anywhere in the file; comments
	56	are delimited by hash marks (``#'') and new lines.
	57	Any unspecified fields will default to null.
	58	.Pp
	59	The first field is the
	60	name of the terminal special file as it is found in
	61	.Pa /dev .
	62	.Pp
	63	The second field of the file is the command to execute for the line,
	64	usually
	65	.Xr getty 8 ,
	66	which initializes and opens the line, setting the speed, waiting for
	67	a user name and executing the
	68	.Xr login 1
	69	program.
	70	It can be, however, any desired command, for example
	71	the start up for a window system terminal emulator or some other
	72	daemon process, and can contain multiple words if quoted.
	73	.Pp
	74	The third field is the type of terminal usually connected to that
	75	tty line, normally the one found in the
	76	.Xr termcap 5
	77	data base file.
	78	The environment variable
	79	.Dv TERM
	80	is initialized with the value by
	81	either
	82	.Xr getty 8
	83	or
	84	.Xr login 1 .
	85	.Pp
	86	The remaining fields set flags in the
	87	.Fa ty_status
	88	entry (see
	89	.Xr getttyent 3 )
	90	or specify a window system process that
	91	.Xr init 8
	92	will maintain for the terminal line.
	93	.Pp
	94	As flag values, the strings ``on'' and ``off'' specify that
	95	.Xr init
	96	should (should not) execute the command given in the second field,
	97	while ``secure'' (if ``on'' is also specified) allows users with a
	98	uid of 0 to login on
	99	this line.
	100	The flags ``local'', ``rtscts'', ``mdmbuf'', and ``softcar''
	101	modify the default behaviour of the terminal line, and their actions
	102	are driver dependent.
	103	The ``local'' flag causes the driver to
	104	treat the line as if it locally connected.
	105	The ``rtscts'' flag
	106	instructs the driver to use RTS/CTS hardware flow control, if
	107	possible.
	108	The ``mdmbuf'' flag instructs the driver to use
	109	DTR/DCD flow control, if possible.
	110	The ``softcar'' flag causes the driver to ignore
	111	hardware carrier on the line.
	112	These flag fields should not be quoted.
	113	.Pp
	114	The string ``window='' may be followed by a quoted command
	115	string which
	116	.Xr init
	117	will execute
	118	.Em before
	119	starting the command specified by the second field.
	120	.Sh EXAMPLES
	121	.Bd -literal
	122	# root login on console at 1200 baud
	123	console "/usr/libexec/getty std.1200" vt100 on secure
	124	# dialup at 1200 baud, no root logins
	125	ttyd0 "/usr/libexec/getty d1200" dialup on # 555-1234
	126	# Mike's terminal: hp2621
	127	ttyh0 "/usr/libexec/getty std.9600" hp2621-nl on # 457 Evans
	128	# John's terminal: vt100
	129	ttyh1 "/usr/libexec/getty std.9600" vt100 on # 459 Evans
	130	# terminal emulate/window system
	131	ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0"
	132	# Network pseudo ttys -- don't enable getty
	133	ttyp0 none network
	134	ttyp1 none network off
	135	.Ed
	136	.Sh FILES
	137	.Bl -tag -width /etc/ttys -compact
	138	.It Pa /etc/ttys
	139	.El
	140	.Sh SEE ALSO
	141	.Xr login 1 ,
	142	.Xr getttyent 3 ,
	143	.Xr ttyslot 3 ,
	144	.Xr gettytab 5 ,
	145	.Xr termcap 5 ,
	146	.Xr getty 8 ,
	147	.Xr init 8 ,
	148	.Xr ttyflags 8
	149	.Sh HISTORY
	150	A
	151	.Nm
	152	file appeared in
	153	.At v6 .