[shells] / banned.8

.TH banned 8 "20 April 1999" "Local tools"
.SH NAME
banned \- tells a user that he's banned
.SH SYNOPSIS
.B banned
.SH USAGE
Set a user's shell to the
.B banned
program's path, and put a file
.B .banned
in his or her home directory (owned by
.B root
by preference).  When the user logs in, he or she will be told to go
away, given the explanation from the
.B .banned
file, and logged out again.  An entry is also made in the system logs,
using the
.B LOG_AUTH
facility.
.PP
Don't put
.B banned
in the
.B /etc/shells
file!
.SH FILES
.TP 5
.B .banned
An explanation given to a user to explain why he or she should go away.
.SH BUGS
None planned.
.SEE ALSO
.BR chrootsh (8),
.BR ushell (1).
.SH AUTHOR
Mark Wooding (mdw@nsict.org)
Commit	Line	Data
ed36b0a2	1	.TH banned 8 "20 April 1999" "Local tools"
	2	.SH NAME
	3	banned \- tells a user that he's banned
	4	.SH SYNOPSIS
	5	.B banned
	6	.SH USAGE
	7	Set a user's shell to the
	8	.B banned
	9	program's path, and put a file
	10	.B .banned
	11	in his or her home directory (owned by
	12	.B root
	13	by preference). When the user logs in, he or she will be told to go
	14	away, given the explanation from the
	15	.B .banned
	16	file, and logged out again. An entry is also made in the system logs,
	17	using the
	18	.B LOG_AUTH
	19	facility.
	20	.PP
	21	Don't put
	22	.B banned
	23	in the
	24	.B /etc/shells
	25	file!
	26	.SH FILES
	27	.TP 5
	28	.B .banned
	29	An explanation given to a user to explain why he or she should go away.
	30	.SH BUGS
	31	None planned.
	32	.SEE ALSO
	33	.BR chrootsh (8),
	34	.BR ushell (1).
	35	.SH AUTHOR
	36	Mark Wooding (mdw@nsict.org)