Return to dm.config.5 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man5

Annotation of 43BSDTahoe/man/man5/dm.config.5, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1988 Regents of the University of California.
                      2: .\" All rights reserved.
                      3: .\"
                      4: .\" Redistribution and use in source and binary forms are permitted
                      5: .\" provided that the above copyright notice and this paragraph are
                      6: .\" duplicated in all such forms and that any documentation,
                      7: .\" advertising materials, and other materials related to such
                      8: .\" distribution and use acknowledge that the software was developed
                      9: .\" by the University of California, Berkeley.  The name of the
                     10: .\" University may not be used to endorse or promote products derived
                     11: .\" from this software without specific prior written permission.
                     12: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
                     13: .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
                     14: .\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
                     15: .\"
                     16: .\"    @(#)dm.config.5 5.4 (Berkeley) 7/9/88
                     17: .\"
                     18: .TH DM.CONFIG 5 "July 9, 1988"
                     19: .UC 5
                     20: .SH NAME
                     21: dm.config \- dm configuration file
                     22: .SH DESCRIPTION
                     23: \fIDm.config\fP is the configuration file for the \fIdm\fP(8) program.
                     24: It consists of lines beginning with one of three keywords, ``badtty'',
                     25: ``game'', and ``time''.  All other lines are ignored.
                     26: .PP
                     27: Any tty listed after the keyword ``badtty'' may not have games played on
                     28: it.  Entries consist of two white-space separated fields: the string
                     29: ``badtty'' and the ttyname as returned by \fIttyname\fP(3).  For example,
                     30: to keep the uucp dialout, ``tty19'', from being used for games, the
                     31: entry would be:
                     32: .PP
                     33: .RS
                     34:        badtty  /dev/tty19
                     35: .RE
                     36: .PP
                     37: Any day/hour combination listed after the keyword ``time'' will disallow
                     38: games during those hours.  Entries consist of four white-space separated
                     39: fields: the string ``time'', the unabbreviated day of the week and the
                     40: beginning and ending time of a period of the day when games may not be
                     41: played.  The time fields are in a 0 based, 24-hour clock.  For example,
                     42: the following entry allows games playing before 8AM and after 5PM on
                     43: Mondays.
                     44: .PP
                     45: .RS
                     46:        time            Monday  8       17
                     47: .RE
                     48: .PP
                     49: Any game listed after the keyword ``game'' will set parameters for a specific
                     50: game.  Entries consist of five white-space separated fields: the keyword
                     51: ``game'', the name of a game, the highest system load average at which the
                     52: game may be played, the maximum users allowed if the game is to be played,
                     53: and the priority at which the game is to be run.  Any of these fields may
                     54: start with a non-numeric character, resulting in no game limitation or
                     55: priority based on that field.  The game "default" controls the settings for
                     56: any game not otherwise listed, and must be the last ``game'' entry in the
                     57: file.  Priorities may not be negative.  For example, the following entries
                     58: limits the game ``hack'' to running only when the system has 10 or less
                     59: users and a load average of 5 or less; all other games may be run any time
                     60: the system has 15 or less users.
                     61: .PP
                     62: .RS
                     63:        game            hack            5       10      *
                     64:        game            default *       15      *
                     65: .RE
                     66: .SH "SEE ALSO"
                     67: setpriority(2), ttyname(3), dm(8)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.