Instructions for Building and Setting up the Server (23-Apr-1998)

Edit the file Server/config.h.in to meet your requirements.  You may choose to
leave this as is for a pure Vanilla default server.

To setup the server to your machine's architecture run the configure program. 
This is a script that will check your system for system dependent differences
and configure the server to deal with these.  It will also prompt you for the
directory into which the server is to be installed.

Configure will make two files for the server to deal with the differences. 
These are config.h and system.mk.  After these are made you may want to check
the files to see if the defines are what you like.  Most people don't need to do
this.

After you have done this then go to the source root directory and do a make
depend. This will setup your makefiles to rebuild an object if any include files
it uses change.

Now you're ready to make the server. Just type make in the source root
directory.

If everything is made ok then type 'make install' to move the files to LIBDIR.

If everything is compiled and in the right locations then proceed to edit the
configuration files for your requirements.  Here are the files and what they do:

	.sysdef 	- tunable parameters
	.time		- playable/clue hours in it
	.banned		- list of players that are banned from server
	.clue-bypass	- list of players that don't have to go through
			  clue checking
	.conquer	- server's conquest stats output
	.features	- list of special features allowed at the server
			  that some clients might have. Some of these
			  features may be considered 'borgish'.
	.motd		- This is the information about the server for the
			  players.
	.motd_clue	- Another motd for clue playing hours.
	.reserved	- RSA public/global key listing for verification

If the install worked then go to the LIBDIR. There are two programs that should
be running all the time. They are:

    1.	newstartd - waits around for a connection from a client. It then forks
	and execs an ntserv.  This also accepts connections from the metaserver
	and via telnet for the current player list.

    2.	update - wakes up once a day and gets a new key list from the metaserver
	port 3530. It then makes a new .reserved through rsa_keycomp and
	reconstructs your .motd file.  [Note that this program need not run if
	you are behind a firewall].

Start these two programs.  Once they are running then try connecting to the
server and check things out.  If there is a problem then check out the
docs/DEBUG.HELP file for possible solutions.

See docs/metaservers-HowTo for soliciting players via the metaservers.
