ntserv

  the server half of the socket protocol.  This code is called by 
  the startup routines.  It can be started by hand as follows, though:

  % netrek -s 2843	/* start a cxtrek on client, specify random socket # */
  Waiting for connection from sequent.berkeley.edu

  /* On server, enter: */
  % ntserv -s 2843 client.berkeley.edu

  This should work.  

  Though It is usually unnecessary, by specifying an optional -R parameter 
  (if you are the one who owns the xtrek stuff), you can request one of the 
  4 unused player slots (reserved for robots, usually).  This was added, 
  because there are often 16 people playing, and I sometimes need to get 
  into the game anyway.  (Or just want to!)

  There is also an example .sysdef file, which is used to define some general
  system defaults (such as which weapons are legal, which planets people appear
  next to, how many players are needed for tournament mode, etc.).  

  options include:

  -s #:			Specify socket number to connect through client through.
  -d machine:		Specify machine to connect to.
  -R:			Specify use of reserved slot.
  -u:			Get usage description.

Installation:
    
    You need to modify the following things to make it work properly:

    - set serverName in data.c the the name of the machine running the server.
    - set the file names as appropriate in defs.h
    - create a .motd file as specified in defs.h for your users to read.  In
	particular, you might want to maintain a list of the highest ranked
	players (see scores in startup/).  A sample .motd is provided.

Known bugs:
    
    1) This version of the code was written with a signal() handler which does
    not reset the handler when a signal is received.  Specifically, the
    SIGALRM signal is used for timing, and if the system you are compiling 
    on resets the handler, then your daemon will crash with a message like
    "Alarm Clock".  To fix it, you have to reset the signals in all of 
    the handlers (if your system's signal() resets the handlers upon 
    reception of a signal).

    2) You may have a problem with the game freezing up
    when a robot joins the game.  If so, you either have to: 1) remove the 
    signal(SIGCHLD, reaper) call in daemonII.c (if your system can survive 
    without it), or 2) remove all calls to check_load in daemonII.c.  This 
    will mean that your game won't shut itself down when the load gets too 
    high (big deal).
