xref: /netbsd/games/hunt/huntd/huntd.6 (revision 6550d01e)
1.\"	$NetBSD: huntd.6,v 1.9 2009/03/11 13:01:49 joerg Exp $
2.\"
3.\" huntd
4.\"
5.\" Copyright (c) 1983-2003, Regents of the University of California.
6.\" All rights reserved.
7.\"
8.\" Redistribution and use in source and binary forms, with or without
9.\" modification, are permitted provided that the following conditions are
10.\" met:
11.\"
12.\" + Redistributions of source code must retain the above copyright
13.\"   notice, this list of conditions and the following disclaimer.
14.\" + Redistributions in binary form must reproduce the above copyright
15.\"   notice, this list of conditions and the following disclaimer in the
16.\"   documentation and/or other materials provided with the distribution.
17.\" + Neither the name of the University of California, San Francisco nor
18.\"   the names of its contributors may be used to endorse or promote
19.\"   products derived from this software without specific prior written
20.\"   permission.
21.\"
22.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
23.\" IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
24.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
25.\" PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
26.\" OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
27.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
28.\" LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
29.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
30.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
31.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
32.\" OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
33.\"
34.Dd April 4, 2001
35.Dt HUNTD 6
36.Os
37.Sh NAME
38.Nm huntd
39.Nd hunt daemon, back-end for hunt game
40.Sh SYNOPSIS
41.Nm
42.Op Fl s
43.Op Fl p Ar port
44.Sh DESCRIPTION
45.Nm
46controls the multi-player
47.Xr hunt 6
48game.
49When it starts up, it tries to notify all members of the
50.Em hunt-players
51mailing list (see
52.Xr sendmail 8 )
53by faking a
54.Xr talk 1
55request from user
56.Dq Hunt Game .
57.Pp
58The
59.Fl s
60option is for running
61.Nm
62forever (server mode).
63This is similar to running it under the control of
64.Xr inetd 8
65(see below), but it consumes a process table entry when no one is playing.
66.Pp
67The
68.Fl p
69option changes the UDP port number used to rendezvous with the player
70process and thus allows for private games of hunt.
71This option turns off the notification of players on the
72.Em hunt-players
73mailing list.
74.Ss INETD
75To run
76.Nm
77from
78.Xr inetd 8 ,
79you'll need to
80.\"put the
81.\".Nm hunt
82.\"service in
83.\".Pa /etc/services :
84.\".Bd -literal
85.\"hunt 26740/udp		# multi-player/multi-host mazewars
86.\".Ed
87.\"and
88uncomment the following line in
89.Pa /etc/inetd.conf :
90.Bd -literal -offset indent -compact
91hunt dgram udp wait nobody /usr/games/huntd huntd
92.Ed
93Do not use any of the command line options; if you want
94.Xr inetd 8
95to start up
96.Nm
97on a private port, change the port listed for
98.Nm hunt
99in
100.Pa /etc/services .
101.Sh NETWORK RENDEZVOUS
102When
103.Xr hunt 6
104starts up, it broadcasts on the local area net
105(using the broadcast address for each interface) to find a
106.Nm hunt
107game in progress.
108If a
109.Nm
110hears the request, it sends back the port number for the
111.Nm hunt
112process to connect to.
113Otherwise, the
114.Nm hunt
115process starts up a
116.Nm
117on the local machine and tries to rendezvous with it.
118.Sh SEE ALSO
119.Xr talk 1 ,
120.Xr hunt 6 ,
121.Xr sendmail 8
122.Sh AUTHORS
123Conrad Huang, Ken Arnold, and Greg Couch;
124.br
125University of California, San Francisco, Computer Graphics Lab
126