The format for the command to invoke sgopher from the command line is
	sgopher [gopherhost [gopherport]]
where gopherhost is the host that the gopher server is running on
and gopherport is the port that the server is running on.  For example;
	sgopher gopher.aedc 70<return>
Before you compile sgopher be sure to change the HOST, PORT, LOGFILE,
GOVCOMP, GOPHPHN, and GOPHADM defines in conf.h.
========================== For UNIX systems ============================
To launch from inetd add the following line to /etc/services
	sgopher		3678/tcp
and add the following line to /usr/etc/inetd.conf or /etc/inetd.conf
	sgopher stream tcp nowait root /usr/local/bin/sgopher sgopher
Of course, you can change the port that it is running on (3678).
========================== For VAX systems ============================
I am a UNIX person so porting sgopher to VAX was a lot of fun.  It
only works with Wollongong WIN/TCP (as far as I know).  I may not have
done things in a standard way.  If any VAX gurus out there want
to give me some tips...  The sources will have to be unpacked on a
UNIX Machine and moved to a directory on the VAX machine.  To build sgopher
under VMS type
	@make<return>
Then, if you wish, copy it into sys$common:, and set up a foreign link like;
	gopher = "$ sys$common:sgopher.exe"
so that you can supply the command line arguments.  This is done in one
of the system start up files.
It can be invoked directly and access the default server with the command
	run sgopher<return>
=======================================================================
I am interested in any changes or problems that you encounter running
or porting this program.  Also, if you find this program useful I would
really appreciate hearing from you.

Sean Fuller					:)
fuller@aedc-vax.af.mil
