1.\" $NetBSD: ttyaction.3,v 1.9 2002/02/07 07:00:52 ross Exp $ 2.\" 3.\" Copyright (c) 1996 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Gordon W. Ross. 8.\" 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the NetBSD 20.\" Foundation, Inc. and its contributors. 21.\" 4. Neither the name of The NetBSD Foundation nor the names of its 22.\" contributors may be used to endorse or promote products derived 23.\" from this software without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 26.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 27.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 28.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 29.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" 37.Dd August 24, 1996 38.Dt TTYACTION 3 39.Os 40.Sh NAME 41.Nm ttyaction 42.Nd ttyaction utility function 43.Sh LIBRARY 44.Lb libutil 45.Sh SYNOPSIS 46.Fd #include \*[Lt]util.h\*[Gt] 47.Ft int 48.Fn ttyaction "char *ttyname" "char *action" "char *username" 49.Sh DESCRIPTION 50The 51.Fn ttyaction 52function is used by 53.Xr login 1 , 54.Xr getty 8 , 55.Xr telnetd 8 56and 57.Xr rlogind 8 58to execute site-specific commands 59when a login session begins and ends. 60.Pp 61The 62.Fn ttyaction 63function scans the 64.Pa /etc/ttyaction 65file for any records that match the current 66.Fa ttyname 67and 68.Fa action 69parameters, and for each matching record, runs the shell command 70shown in that record. The record format is described in 71.Xr ttyaction 5 . 72The parameter 73.Fa username 74is the name of the new owner of the 75.Fa ttyname 76device. Note that the 77.Fa ttyname 78parameter may be passed as a fully qualified pathname, and the 79.Fn ttyaction 80function will skip the leading "/dev/" part of the string. 81(This is a convenience for login and getty.) 82.Sh RETURN VALUES 83.Fn ttyaction 84returns the status of the last command it executed, 85or zero if no matching commands were found. 86.Sh FILES 87.Bl -tag -width /etc/ttyaction -compact 88.It Pa /dev/\(** 89.It Pa /etc/ttyaction 90.El 91.Sh SEE ALSO 92.Xr ttyaction 5 93.Sh AUTHORS 94The following people contributed to this design: 95.Bd -literal -offset indent 96Gordon W. Ross \*[Lt]gwr@netbsd.org\*[Gt] 97Chris G. Demetriou \*[Lt]cgd@netbsd.org\*[Gt] 98Ty Sarna \*[Lt]tsarna@endicor.com\*[Gt] 99.Ed 100.Sh BUGS 101There should be some 102.Em other 103mechanism to allow selection of different access control policies 104on a per-line basis. It has been suggested that the same 105.Nm ttyaction 106mechanism should also be used for determining access control, but 107it was decided (after much discussion) that 108.Nm ttyaction 109should only describe actions to be performed 110.Em after 111the system has decided to change the ownership of some tty. 112Access control policies will be handled by a separate mechanism. 113