gopherrc(5) [debian man page]
GOPHERRC(5) File Formats Manual GOPHERRC(5) NAME
gopherrc - configuration file for gopher(1) DESCRIPTION
The gopherrc file contains a list of directives that alter the behaviour of the gopher(1) client. It is composed of lines of the form: Token: Value Tokens are case insensitive and the value field will change, depending on the token. A pound sign ("#") at the beginning of a line signi- fies a comment line. Gopherrc files are used in a number of places. There is a global gopherrc file (called gopherrc). This is usually placed in a systemwide directory. A file with the same format called remotegopher.rc is also used by the gopher client when using the -r switch. Also, an individual has their own customized version of this file in their home directory in the file .gopherrc. On VMS this file is called GOPHERRC. All of these files use the format described below. Most people will set the values in this file by pressing the 'O' key to set options in the curses gopher client, rather than editing this file directly. People considering editing this file on VMS should make sure their editor preserves the Stream_LF format of the file. Quick pseudo grammar map: <content type>,<display command>,<print command> SearchBolding: <yes|no> Bookmarks: <bookmarks> The following tokens are recognized map: maps a content type (such as text/plain, or image/gif) to commands to execute for displaying the document or printing the document, i.e. The content type, display command, and printing command are separated by commas. The sequence of %s is replaced with the filename of a temporary file containing the document to be printed or viewed. If the command starts with the vertical bar (|) the command will be executed immediately and the document will be sent to the commands standard input. Note this feature does not work on VMS. If the display command is set to 'builtin', then the text file pager inside the gopher client will be used to display the item. SearchBolding: controls the clients display of search terms. If the value is 'yes', then search words will be bolded. Otherwise they'll be left alone. Bookmarks: The bookmarks in .link format follow. For more information on the format of a .link file, consult the gopherd(8) manual page. Sample gopherrc file: map: text/plain,builtin,lpr %s map: image/gif,xv %s, Bookmarks: Type=1 Name=Bookmark #1 Host=gopher.tc.umn.edu Port=70 Path= # Type=0+ Name=textfile Host=foo.com Path=0/readme Port=70 SEE ALSO
Media Type Registration Procedure, March 1994, RFC 1590 gopher(1),gopherd(8) GOPHERRC(5)
Check Out this Related Man Page
GO500(8C) GO500(8C) NAME
go500 - Local Gopher index search to X.500 search gateway SYNOPSIS
/usr/sbin/go500 [-b searchbase] [-d level] [-l] [-x hostname] [-c rdncount] [-f filterfile] [-t templatefile] [-p port] [-I] DESCRIPTION
go500 is the local gopher index search to X.500 search daemon. It looks like a gopher index server to a gopher client, translating the search criteria it is given into a search of a pre-configured portion of the X.500 directory. It uses LDAP to talk to X.500. By default, it listens on port 5555 for connections from gopher clients. The go500 server can be run either from inetd(8) or as stand-alone server. STAND-ALONE OPERATION To start go500 as a stand-alone server, simply start it with no arguments /usr/sbin/go500 If you would like to start it at boot time add some lines like this to the etc/rc.local or equivalent file: if [ -f /usr/sbin/go500 ]; then /usr/sbin/go500; echo ' go500' fi OPERATION WITH INETD
To arrange to have go500 started from inetd(8), the Internet protocol daemon, add a line like the following to your /etc/services file, or the equivalent: go500 5555/tcp go500 Next, add a line like this to your /etc/inetd.conf file, or the equivalent: go500 stream tcp nowait nobody /usr/sbin/go500 go500 -I For these changes to take effect with inetd, you will probably have to send it it a HUP signal. See inetd(8) for more details. GOPHER CONFIGURATION
The next step is to configure your local gopher server to have an entry for go500. With the standard unix gopher server, this can be done with a .link file. A sample .link file is given below, with the things you should change given in <>'s: Name=<Label of your choice> Type=7 Port=5555 Path= Host=<host.running.go500.here> You may also have to restart your gopher daemon, or remove the .cache file. See gopherd(8) for more details. OPTIONS
-b searchbase Specify an alternate starting point for searches. The argument should be a Distinguished Name in the form defined by RFC 1485. For example, the DN "o=University of Michigan, c=US" could be given to search the University of Michigan portion of the X.500 tree. -d level Turn on debugging as defined by level. If this option is specified, go500 will not fork or disassociate from the invoking terminal. Some general operation and status messages are printed for any value of level. level is taken as a bit string, with each bit corre- sponding to a different kind of debugging information. -f filterfile Specify an alternate filter configuration file for use with the ldap_getfilter(3) facility, used by go500. -l Enable logging of various status and errors to the LOG_DAEMON facility via syslog(8). -p port Specify an alternate port on which to listen for connections. -t templatefile Specify an alternate template configuration file for use with the ldap_init_templates(3) facility, used by go500. -c rdncount Specify the number of DN components to show for the names and DN attributes within entries matching the search. -x hostname Specify an alternate host on which the ldap server is running. -I Run from inetd(8). NOTES
Some implementations of inetd have a small limit on the number of arguments that can be specified in the /etc/inetd.conf(5) file. This can cause problems if you are using go500 with a lot of arguments. The default values for most of the things you can specify with options are configured at compile time in the include/ldapconfig.h.edit include file. SEE ALSO
ldap(3), inetd(8), gopherd(8), go500gw(8) ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan LDAP 3.3 Release. OpenLDAP 2.0.27-Release 20 August 2000 GO500(8C)