RSA notes:  
--------- 

The following applies because it is illegal to export RSA from the US.  We
apologize for any invonvenience. You could, I suppose, complain to the NSA ;-)

If you want to run RSA verification you will need to get the res-rsa package
from an appropriate ftp site. You will need to copy or make a link to
ntserv/rsa_utilmp.c from rsa_utilmp.c in the res-rsa package. Then just
define all the RSA stuff in your .mk file and 'make install' and it should
run fine (you should check defs.h and change RSA_KEY_FILE appropriately as
well). res-rsa is currently available on pittslug.sug.org. A European
flavour of rsa_util.c is _apparently_ available on castlab.engr.wisc.edu and
melmac.uni-linz.ac.az (but I have not checked into it). You will alse need
to get yourself a keyfile - probably from pittslug.sug.org as well. The 
metaserver also provides a key file if you connect to the right port 
(telnet charon.amdahl.com 3530). Look in the tools directory at the files
rsa_keycomp and rsa_getkeys. Those will help you set up an RSAreserved file
(note: if you do not have an RSAreserved file when you try to connect to the
server the client will complain...).

How to set up an INL server:
----------------------------

	The INL server should install and compile without much problem
on most machines.  Change into the config directory and make a
symbolic link from your system version's .mk file to 'system.mk'. Eg.
on my machine (a decstation running ultrix) I do 'cd config' then 'ln
-s ultrix.mk system.mk' You will also need to make a link to
reserved.c from reserved.c.shipped (ln -s reserved.c.shipped
reserved.c) in the ntserv directory.  Next edit the system.mk file to
reflect specific details about your site and compilation #defines that
you want (look at ultrix.mk for most up-to-date options). In principle
you might be able to get away with just changing XTREKDIR. If you do
not want RSA support then edit your system.mk file and remove all the
RSA defines.  If you like, also edit motd_local and sample_sysdef (if
you didn't install RSA you have to set CONFIRM=0) and sample_time to
reflect what you want your site specifics. After you have one your
editing you can run 'checklist' to give you an idea if you forgot
anything.

Then from the top INL directory, type 'make depend' then 'make install'.
Once installed and running successfully you can type 'make clean' and leave
it at that. If you apply patches you may need to do 'make depend' followed
by a 'make install'. If there are any compiler errors during installation,
contact the INL server hack, so that future versions can be fixed. 

	Also available are nuke -- to immediately clear player slots,
xtkill -- to obliterate hosers in the game, and xsg -- to watch the game
in progress. Some of these should be installed when you do 'make install'.
A version of xsg that will compile and install with the INL server is
available from crissy.berkeley.edu:/pub/xsg2.1-INL.tar.gz.
It should be downloaded into the toplevel INL directory and a symbolic made 
from its directory to 'xsgd' (i.e. 'ln -s ./xsg2.1-INL xsgd')

    You may need to edit register_tourney slightly.  It uses Mail,
which may not be available on all machines. The tools directory has 
several other random utilities in it which are really not necessary 
unless you want to hack the planet layout or something like that- and
if you do then you can probably figure out how to build them on your 
own ;-)

Running an INL _AND_ a regular server on the same machine
---------------------------------------------------------
If you desire to do this all you need to do is change PKEY in defs.h to
something different from what the other server uses. For example you might
want to make your regular server use PKEY=128 and the INL server use PKEY=10.
Be advised that you will need to compile 2 versions of most tools (one for 
each server).

Starting and Ending Tournaments:
--------------------------------

	Starting a tournament is simple.  Go to the bin directory, and run
start_tourney.  It will examine the contents of your .ports file in that 
directory and start accepting connections on the specified ports. A sample
ports file is in the ntstart directory. It's pretty self explanatory.

	Each time an "official" INL game is played, the daemon will move
the .players, .global, and other files to backup locations, in case the
server god wants to look at them.  It will also create an inl_log and
inl_stats file.  These should be sent to the Statboy.  The register_tourney
script will do this automatically if both teams agreed with the REGISTER
command that this is an official game. Otherwise you have to run 
register_tourney by hand.

For example, if the log and stats files are INL_log.3478 and INL_stats.3478,
then to register an official tourney with the INL Statboy, run
"register_tourney 3478". This is only necessary if, during the game, the
'register' command wasn't used - if it was the stats should be automatically
sent to the stat boy.

	Questions and comments can be sent to ihc@cs.montana.edu
	(but first read the file 'Bugs' so you're not telling us 
	something we know already)

Ray Jones	(originally)
ERic mehlhaff	(spring93 server hacker-dude)
J. Mark Noworolski (hacker/organizer)


Special comments:
----------------
If your system doesn't have SYS V typed shared memory, but it can
mmap regular files, then add -DUSE_MMAP to EXTRACFLAGS.  Also, if
your system does not have memalign, but does have valloc add -DUSE_VALLOC.
(Our old sequent needs -DUSE_MMAP -DUSE_VALLOC -DMAP_FIXED=0.)
When the daemon starts up it will create a file sharedMem in the
current directory.  It's a good idea to make sure the sharedMem file
is on a local filesystem (i.e. not on an NFS filesystem).

        -Sam

The optimizer on decstations with either gcc or cc has sometimes 
(inermittently it seems) given me major problems. Compile with -O at your
own risk (this seems cured with gcc2.3.2 or later I presume).
		- jmn

INL Games
----------
MAKE SURE ALL OF YOUR DEFAULTS IN .sysdef are set correctly when you have
an INL game. Also double check that .feature doesn't enable any info-borg
features in clients.

