[shells] / banned.8

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