dm(8) [netbsd man page]

DM(8)							    BSD System Manager's Manual 						     DM(8)

NAME

     dm -- dungeon master

SYNOPSIS

     ln -s dm game

DESCRIPTION

     dm is a program used to regulate game playing.  dm expects to be invoked with the name of a game that a user wishes to play.  This is done by
     creating symbolic links to dm, in the directory /usr/games for all of the regulated games.  The actual binaries for these games should be
     placed in a ``hidden'' directory, /usr/games/hide, that may only be accessed by the dm program.  dm determines if the requested game is
     available and, if so, runs it.  The file /etc/dm.conf controls the conditions under which games may be run.

     The file /etc/nogames may be used to ``turn off'' game playing.  If the file exists, no game playing is allowed; the contents of the file
     will be displayed to any user requesting a game.

FILES

     /etc/dm.conf	 configuration file
     /etc/nogames	 turns off game playing
     /usr/games/hide	 directory of ``real'' binaries
     /var/log/games.log  game logging file

SEE ALSO

     dm.conf(5)

HISTORY

     The dm command appeared in 4.3BSD-Tahoe.

SECURITY CONSIDERATIONS

     Two issues result from dm running the games setgid ``games''.  First, all games that allow users to run UNIX commands should carefully set
     both the real and effective group ids immediately before executing those commands.  Probably more important is that dm never be setgid any-
     thing but ``games'' so that compromising a game will result only in the user's ability to play games at will.  Secondly, games which previ-
     ously had no reason to run setgid and which accessed user files may have to be modified.

BSD
								   May 31, 1993 							       BSD

DM.CONF(5)						      BSD File Formats Manual							DM.CONF(5)

NAME

     dm.conf -- dungeon master configuration file

DESCRIPTION

     The dm.conf file is the configuration file for the dm(8) program.	It consists of lines beginning with one of three keywords, badtty, game,
     and time.	All other lines are ignored.

     Any tty listed after the keyword badtty may not have games played on it.  Entries consist of two white-space separated fields: the string
     badtty and the ttyname as returned by ttyname(3).	For example, to keep the uucp dialout, ``tty19'', from being used for games, the entry
     would be:

	   badtty  /dev/tty19

     Any day/hour combination listed after the keyword time will disallow games during those hours.  Entries consist of four white-space separated
     fields: the string time, the unabbreviated day of the week and the beginning and ending time of a period of the day when games may not be
     played.  The time fields are in a 0 based, 24-hour clock.	For example, the following entry allows games playing before 8AM and after 5PM on
     Mondays:

	   time    Monday  8	   17

     Any game listed after the keyword game will set parameters for a specific game.  Entries consist of five white-space separated fields: the
     keyword game, the name of a game, the highest system load average at which the game may be played, the maximum users allowed if the game is
     to be played, and the priority at which the game is to be run.  Any of these fields may start with a non-numeric character, resulting in no
     game limitation or priority based on that field.

     The game default controls the settings for any game not otherwise listed, and must be the last game entry in the file.  Priorities may not be
     negative.	For example, the following entries limits the game ``hack'' to running only when the system has 10 or less users and a load aver-
     age of 5 or less; all other games may be run any time the system has 15 or less users.

	   game    hack 	   5	   10	   *
	   game    default	   *	   15	   *

FILES

     /etc/dm.conf  The dm(8) configuration file.

SEE ALSO

     setpriority(2), ttyname(3), dm(8)

BSD
								   May 31, 1993 							       BSD