GASH 1.0 CONTROL FILES
18 September 1994
ARL:UT Computer Science Division
Dean Kennedy & Jonathan Abbey
---------------------------------

The following control files should be present in your GASHDIR when you
first try to run GASH.  We have provided samples for each of these files
that you will need to modify for your circumstances.

shell_paths

This file is a simple listing of the shells which you want to support
across your network computing environment.  cua and mua will use this
list to provide GASH administrators a choice of standard shells.  This
file should include the full path to the shell.  See the file if you
have any questions.  The shell_paths file should not contain any kind
of comment lines.

networks_by_room

The networks_by_room file is necessary for the systems code.  This
file contains a list of all rooms that you might have TCP/IP systems
in, along with the IP network or networks that are connected to that
room, and the DNS domain name to be appended to hosts placed on one of
those IP networks.  See the sample file provided for structure.  The
networks_by_room file does accept # comment lines.

internet_assignment

As mentioned in INSTALLATION, the internet_assigment file contains a
list of system types and a class C subrange that determines what IP
address will be assigned to systems of that type.

motd

This message is presented to any user who successfully logs into GASH.

mail_control

This file contains a list of event codes that GASH can generate mail
for, and a list of GASH users/administrators who should receive mail
whenever an event of that type occurs.  If no users are listed for an
event type, mail may still be generated for that event category if
GASH determines that a user or users should be notified.  For example,
if you add a user to a group and Gash_mod_group has no users
associated with it, GASH will still send the user that was added a
notice that he was added.

If the last entry in a mail_control line is **self** the administrator
who was running GASH when the event occurred will receive a copy of
the mail message.

Two mail_control events are of particular interest.  The first is
"Internal_GASH_Error".  Events of this type are generated whenever
GASH detects something that just plain shouldn't have happened.  The
GASH code is strewn with checks that can cause an Internal_GASH_Error.
These are mostly parameter and sanity checks.  There are still some
places in GASH where these messages can be generated without really
meaning anything very bad.  The only one I can think of at the moment
is that when an administrator tries to add an entry to a netgroup, if
the entry won't fit in the 1k char limit, GASH will raise an internal
error, even though this really isn't a GASH logic problem.  We will
fix this in a later release.

The second mail_control event of interest is AUTOGASH, which should
have a list of users to receive the nightly AUTOGASH report.

