Grex Info Conference

View Responses

Grex Info Item 169: Gopher Question...
Entered by wirehead on Fri Jul 15 01:47:57 UTC 1994:

How does one go about setting up a gopher server?

7 responses total.

#1 of 7 by srw on Fri Jul 15 07:24:10 1994:

Well, in general, first one locates an ftp site containing free or public
domain software for the gopher server. There are probably several choices
for this, and it is a good idea to read their notes and choose the most
appropriate one.

Then you ftp the software, and unpack and 'make' it, which will compile
it and link it, thus building an executable. If it is to be a real 
gopher server, it will be listening to the gopher port (70) which
requires that the server be started by someone with root access.

One you have tested it out, you will want to arrange for it to be started
whenever the system is rebooted. It would then run disconnected from any
tty, i.e., as a daemon). This is done by editing certain system files
usually /etc/rc.local  .

Specifically, if you wish to install a gopher server on grex, which listens to
port 70, you should enter an item in coop to discuss the merits of such a
thing. If there is a consensus that it would be a good thing, then you
will get help from the grac staff to make it happen. If you wish to run
a private server on Grex, one that uses a non-restricted port, you need 
first to get permission from the staff. I would guess that this is not
likely toobe approved, but if the reasons are compelling enough, who knows.

Are you aware that grex does run an http daemon? We are listed in the
"Computing" section of the "by subject" listings on the World Wide Web.
Users who are familiar with the html language used to write hypertext
for the WWW may have their own private home page.

#2 of 7 by popcorn on Fri Jul 15 11:38:50 1994:

This response has been erased.

#3 of 7 by davel on Fri Jul 15 12:15:46 1994:

I don't think so, but I really don't know.

#4 of 7 by mju on Fri Jul 15 15:22:20 1994:

No, I don't think Grex is running a Gopher server.  As srw said, we
are running an HTTP server and accessible through WWW, and we are
also accessible *through* gopher (via systems like the MSU gopher),
but we're not actually running our own gopher server.

#5 of 7 by tsty on Fri Jul 15 16:11:16 1994:

Speaking of gopher - and you may want to suggest that I post this
in an additional iten/.cf somewhere; When teh msu-gopher says
that it is going doewn for a backup (at about midnight every night),
it does NOT mean that you have to get off. 
  
It's a bit confusing, but it it IS different from Grex going down
for a backup.
  
Ignore the msu-gopher backup messages, tehy con't count around here.

#6 of 7 by robh on Sat Jul 16 01:23:55 1994:

If you run the Unix command "gopher" on Grex, you will be connected
to the U of Minnesota gopher.  This is not the same as Grex having
a gopher server on-line.

#7 of 7 by srw on Sat Jul 16 07:09:22 1994:

Indeed not. We do have the "gopher" program, which is a gopher *client*.
It's not the only one. Lynx will also function as a gopher client.

Response not possible - You must register and login before posting.