VI.e Setting up Scripts
-----------------------
Occasionally it is useful to have a script executed and its output be returned
as a simple text file.  This is accomplished by building an OS-specific
command file and declaring it to the Gopher server as a text file.  When the
server senses that the text file to be printed is actually a script, it will 
execute the script with a log file, then return that log file as if it were 
the text file requested by the client.  For example, perl and gawk scripts, or
DCL command streams ranging from simple to complex, may be useful.

OS-specific security measures should be taken to insure that a client can only
request execution of a script which the server's management *wants* to be
performed.  In the case of the OpenVMS Gopher Server, these scripts must end
with the extension ".SCRIPT", much just like shell searches require the
extension ".SHELL", even though under OpenVMS both of them might normally have
the extension ".COM".  They must also have the text "$!" as the first two
characters of the first line of the file.  It is also advisable that they be
restricted in access so the server can only execute them when appropriate,
using ACL lists and other OpenVMS security facilities.

.