386BSD 0.1 development
[unix-history] / usr / othersrc / games / dm / dm.8
CommitLineData
7b089094
WJ
1.\" Copyright (c) 1987, 1991 Regents of the University of California.
2.\" 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.\" @(#)dm.8 5.11 (Berkeley) 7/23/91
33.\"
34.Dd July 23, 1991
35.Dt DM 8
36.Os
37.Sh NAME
38.Nm dm
39.Nd dungeon master
40.Sh SYNOPSIS
41.Nm ln
42.Fl s Cm dm Ar game
43.Sh DESCRIPTION
44.Nm Dm
45is a program used to regulate game playing.
46.Nm Dm
47expects to be invoked with the name of a game that a user wishes to play.
48This is done by creating symbolic links to
49.Nm dm ,
50in the directory
51.Pa /usr/games
52for all of the regulated games.
53The actual binaries for these games should be placed in a
54.Dq hidden
55directory,
56.Pa /usr/games/hide ,
57that may only be accessed by the
58.Nm dm
59program.
60.Nm Dm
61determines if the requested game is available and, if so, runs it.
62The file
63.Pa /etc/dm.conf
64controls the conditions under which games may
65be run.
66.Pp
67The file
68.Pa /etc/nogames
69may be used to
70.Dq turn off
71game playing.
72If the file exists, no game playing is allowed; the contents of the file
73will be displayed to any user requesting a game.
74.Sh FILES
75.Bl -tag -width /var/log/games.log -compact
76.It Pa /etc/dm.conf
77configuration file
78.It Pa /etc/nogames
79turns off game playing
80.It Pa /usr/games/hide
81directory of ``real'' binaries
82.It Pa /var/log/games.log
83game logging file
84.El
85.Sh SEE ALSO
86.Xr dm.conf 5
87.Sh BUGS
88Two problems result from
89.Nm dm
90running the games setuid
91.Dq games .
92First, all games that allow users to run
93.Tn UNIX
94commands should carefully
95set both the real and effective user id's immediately before executing
96those commands. Probably more important is that
97.Nm dm
98never be setuid
99anything but
100.Dq games
101so that compromising a game will result only in
102the user's ability to play games at will. Secondly, games which previously
103had no reason to run setuid and which accessed user files may have to
104be modified.
105.Sh HISTORY
106The
107.Nm dm
108command appeared in
109.Bx 4.3 tahoe .