huntd — hunt
daemon, back-end for hunt game
huntd controls the multi-player
-a addr option
is used to cause the server to listen only on a specific interface address.
The addr argument must be given as an IP address.
-b option is specified,
huntd will fork and go into the background. In this
mode, errors will be logged via syslog instead of to
Options given with
-D override those read
from configuration files (see
-p port option
changes the UDP port number used to rendezvous with the player process and
thus allows for private games of
-s option is for running
huntd forever (server mode). This is similar to
running it under the control of inetd(8)
(see below), but it consumes a process table entry when no one is playing,
and monitor clients are not disconnected.
inetd(8), you'll need to add this line to
hunt dgram udp wait nobody /usr/games/huntd HUNT
Do not use any of the command line options — if you want
inetd(8) to start up
huntd on a private port, change the port listed in
When hunt(6) starts up, it
broadcasts on attached networks, using the broadcast or point-to-point
destination address for each interface, to find a
hunt game in progress. If a
huntd hears the request, it sends back the port
number for the
hunt process to connect to.
huntd starts, it looks for
configuration files that determine game parameters. Each line of a
configuration file is of the form var
= value. Comments start with a
hash sign (‘#’). The configuration files loaded in order (if
they exist) are: /etc/hunt.conf,
Many of these variables require intimate knowledge of the driver source code. The complete list of configurable variables is as follows.
Conrad Huang, Ken
Arnold, and Greg Couch;
University of California, San Francisco, Computer Graphics Lab
David Leonard tidied up, and added the configuration file.
|September 25, 2015||OpenBSD-current|