fix bad mdoc reference & clean up a little
This commit is contained in:
parent
c4b0f47514
commit
a3a66ff007
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: dm.conf.5,v 1.3 1995/03/21 15:09:07 cgd Exp $
|
||||
.\" $NetBSD: dm.conf.5,v 1.4 1998/04/28 18:34:12 fair Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1988, 1991, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
|
@ -38,50 +38,72 @@
|
|||
.Os BSD 4.2
|
||||
.Sh NAME
|
||||
.Nm dm.conf
|
||||
.Nd \&dm configuration file
|
||||
.Nd dungeon master configuration file
|
||||
.Sh DESCRIPTION
|
||||
The
|
||||
.Xr dm.conf
|
||||
file
|
||||
is the configuration file for the
|
||||
.Xr \&dm 8
|
||||
.Xr dm 8
|
||||
program.
|
||||
It consists of lines beginning with one of three keywords, ``badtty'',
|
||||
``game'', and ``time''. All other lines are ignored.
|
||||
It consists of lines beginning with one of three keywords,
|
||||
.Em badtty ,
|
||||
.Em game ,
|
||||
and
|
||||
.Em time .
|
||||
All other lines are ignored.
|
||||
.Pp
|
||||
Any tty listed after the keyword ``badtty'' may not have games played on
|
||||
it.
|
||||
Any tty listed after the keyword
|
||||
.Em 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
|
||||
.Em badtty
|
||||
and the ttyname as returned by
|
||||
.Xr ttyname 3 .
|
||||
For example,
|
||||
to keep the uucp dialout, ``tty19'', from being used for games, the
|
||||
entry would be:
|
||||
to keep the uucp dialout,
|
||||
.Dq tty19 ,
|
||||
from being used for games, the entry would be:
|
||||
.Bd -literal -offset indent
|
||||
badtty /dev/tty19
|
||||
.Ed
|
||||
.Pp
|
||||
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.
|
||||
Any day/hour combination listed after the keyword
|
||||
.Em time
|
||||
will disallow games during those hours.
|
||||
Entries consist of four white-space separated fields: the string
|
||||
.Em 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:
|
||||
.Bd -literal -offset indent
|
||||
time Monday 8 17
|
||||
.Ed
|
||||
.Pp
|
||||
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
|
||||
Any game listed after the keyword
|
||||
.Em game
|
||||
will set parameters for a specific game.
|
||||
Entries consist of five white-space separated fields: the keyword
|
||||
.Em 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.
|
||||
.Pp
|
||||
The game
|
||||
.Em default
|
||||
controls the settings for
|
||||
any game not otherwise listed, and must be the last
|
||||
.Em game
|
||||
entry in the file.
|
||||
Priorities may not be negative.
|
||||
For example, the following entries
|
||||
limits the game
|
||||
.Dq hack
|
||||
to running only when the system 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.
|
||||
.Bd -literal -offset indent
|
||||
|
@ -92,7 +114,7 @@ game default * 15 *
|
|||
.Bl -tag -width /etc/dm.conf -compact
|
||||
.It Pa /etc/dm.conf
|
||||
The
|
||||
.Xr \&dm 8
|
||||
.Xr dm 8
|
||||
configuration file.
|
||||
.El
|
||||
.Sh SEE ALSO
|
||||
|
|
Loading…
Reference in New Issue