Automatically generated from hunt/huntd/huntd.6.in. Do not edit. $NetBSD: huntd.6,v 1.7 2003/06/11 12:00:22 wiz Exp $ huntd Copyright (c) 1983-2003, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: + Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer....
NAMEhuntd - hunt daemon, back-end for hunt game
[-s ] [-p port ]
DESCRIPTIONcontrols the multi-player hunt(6) game. When it starts up, it tries to notify all members of the hunt-players mailing list (see sendmail(8)) by faking a talk(1) request from user ``Hunt Game''
The -s option is for running 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.
The -p option changes the UDP port number used to rendezvous with the player process and thus allows for private games of hunt. This option turns off the notification of players on the hunt-players mailing list.
INETDTo run from inetd(8), you'll need to put the hunt service in /etc/services
hunt 26740/udp # multi-player/multi-host mazewarsand add the following line to /etc/inetd.conf
Do not use any of the command line options; if you want inetd(8) to start up on a private port, change the port listed for hunt in /etc/serviceshunt dgram udp wait nobody /usr/sbin/huntd huntd
NETWORK RENDEZVOUSWhen hunt(6) starts up, it broadcasts on the local area net (using the broadcast address for each interface) to find a hunt game in progress. If a hears the request, it sends back the port number for the hunt process to connect to. Otherwise, the hunt process starts up a on the local machine and tries to rendezvous with it.
SEE ALSOtalk(1), hunt(6), sendmail(8)
AUTHORSConrad Huang, Ken Arnold, and Greg Couch;
University of California, San Francisco, Computer Graphics Lab