From f65aa5bd93d8c7bdb21abf58a237a09c3ecbd8e0 Mon Sep 17 00:00:00 2001 From: mycroft Date: Thu, 20 May 1993 10:10:07 +0000 Subject: Clean up deleted files. --- dm/dm.0 | 66 ------------------------------------------------------------ dm/dm.conf.0 | 66 ------------------------------------------------------------ 2 files changed, 132 deletions(-) delete mode 100644 dm/dm.0 delete mode 100644 dm/dm.conf.0 (limited to 'dm') diff --git a/dm/dm.0 b/dm/dm.0 deleted file mode 100644 index 7afb5634..00000000 --- a/dm/dm.0 +++ /dev/null @@ -1,66 +0,0 @@ -DM(8) 386BSD System Manager's Manual DM(8) - -NNAAMMEE - ddmm - dungeon master - -SSYYNNOOPPSSIISS - llnn --ss ddmm _g_a_m_e - -DDEESSCCRRIIPPTTIIOONN - DDmm is a program used to regulate game playing. DDmm expects to be invoked - with the name of a game that a user wishes to play. This is done by cre- - ating symbolic links to ddmm, in the directory /_u_s_r/_g_a_m_e_s for all of the - regulated games. The actual binaries for these games should be placed in - a ``hidden'' directory, /_u_s_r/_g_a_m_e_s/_h_i_d_e, that may only be accessed by the - ddmm program. DDmm determines if the requested game is available and, if so, - runs it. The file /_e_t_c/_d_m._c_o_n_f controls the conditions under which games - may be run. - - The file /_e_t_c/_n_o_g_a_m_e_s 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. - -FFIILLEESS - /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 - -SSEEEE AALLSSOO - dm.conf(5) - -BBUUGGSS - Two problems result from ddmm running the games setuid ``games''. First, - all games that allow users to run UNIX commands should carefully set both - the real and effective user id's immediately before executing those com- - mands. Probably more important is that ddmm never be setuid anything but - ``games'' so that compromising a game will result only in the user's - ability to play games at will. Secondly, games which previously had no - reason to run setuid and which accessed user files may have to be modi- - fied. - -HHIISSTTOORRYY - The ddmm command appeared in 4.3BSD-Tahoe. - -BSD Experimental July 23, 1991 2 - - - - - - - - - - - - - - - - - - - - - diff --git a/dm/dm.conf.0 b/dm/dm.conf.0 deleted file mode 100644 index 3a1e3648..00000000 --- a/dm/dm.conf.0 +++ /dev/null @@ -1,66 +0,0 @@ -DM.CONF(5) 386BSD Programmer's Manual DM.CONF(5) - -NNAAMMEE - ddmm..ccoonnff - dm configuration file - -DDEESSCCRRIIPPTTIIOONN - 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 Mon- - days. - - time Monday 8 17 - - Any game listed after the keyword ``game'' will set parameters for a spe- - cific 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 limi- - tation 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 sys- - tem has 10 or less users and a load average 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 * - -FFIILLEESS - /etc/dm.conf The dm(8) configuration file. - -SSEEEE AALLSSOO - setpriority(2), ttyname(3), dm(8) - -4.2 Berkeley Distribution May 10, 1991 2 - - - - - - - - - - - - - - - -- cgit v1.2.3-56-ge451