INSTALLATION INSTRUCTIONS FOR 'NETLOG'
=====================================

Most of the configuration is done in the 'Makefile' and in the 'netlog.h'
include file. All customizable parameters are well documented. Edit these
files before typing 'make'.

'grep_record' is in its own sub-directory with its own tests and
instructions. In the event that some tests fail, look under the subdirectory
'greprecord' for more instructions.

Makefile
--------
1. Decide on a toplevel directory under which the software will be installed.
   This directory must be writable by the owner of the program (I_OWNER). It is
   advised to create a unique uid and group for this program ('netlog').

   Define TOPDIR to this toplevel directory.

2. Define I_OWNER as the owner of the program. This user should also belong 
   to group I_GROUP. Only this UID can run 'netlog_indexer' - the indexing
   program.

3. Define I_GROUP as the group of all the netlog files. This has special
   significance since the program is installed with the 'group_id' bit set. If
   the person running the program belongs to one of OKGROUP (defined in
   netlog.h), then the program will 'sgid' to I_GROUP.

   I_GROUP does not have to be included in OKGROUPS. However, do make sure
   that the primary group for I_OWNER is I_GROUP (for sanity).


4. Define NFS if this program will be on a shared disk and accessed from
   multiple systems.

5. Define DEBUG if you want to allow using the '-d' option on the command
   line. When run with the 'debug' option, netlog displays the users' groups,
   and commands that would be executed. If this is not defined, then the '-d'
   option will be ineffective in 'netlog'.


netlog.h
--------

1. Define either the exact path of the needed programs on your system (you
   can use the Unix command 'which' to locate these on your system), or else
   define the full BINPATH. Note that you can use either 'enscript' or 'lpr'
   as the print command.

2. Define WRITE_GROUPS to be the list of groups on your system that can make
   netlog entries. If a user belongs to *any* one of these groups, the program
   sets its group to match the effective group (I_GROUP in the Makefile) since
   its group id bit is set.

   In the minimum case, you can set this to be the same as I_GROUP.

3. Define the NETUMASK depending on who can read/write the various log files.
   Note that the Makefile installs directories with write permission to the
   group, so if you want to use this for a single user, then edit Makefile so
   that the directories are created without g+w and set the NETUMASK to match.
   Note that a umask of '022' means that only a single user can make entries.
   A value of 002 is good if you want 'others' to be able to read the logs,
   or else set to 007 if you don't want 'others' to be able to read logs.

4. Define PROMPTMAIL[12] to email addresses who should get the netlog entries
   via email. The user making the entry is prompted before the entry is mailed
   out. Undefine (or comment them out) if you don't want any default prompts.

5. Define MAINTMAIL to the email address of a person who gets maintenance
   messages from 'netlog' (like archiving of old logs, error in creating
   entries, etc.).

6. Check the values of GOODTERMINALS and BADTERMINALS in case these are not
   in your /etc/ttytab.

7. Set BINPATH to the pathname that should be pre-pended to the user's path
   (when they are running netlog). BINDIR is always prepended since that is
   where 'grep_record' and 'netlog-indexer' are stored. You can set this to the
   null string if all programs are fully qualified. If you do define this, then
   make sure that you have the ':' at the end.

8. Define MAXTKTDATES to be the maximum number of dates (not entries) that
   any ticket can have entries for. Thus, if defined to 15, a ticket can have
   entries on 15 different dates. After this, the user is advised to open a new
   ticket.

   Note that 15 is an adequate number for most applications. The size of the
   index file is dependent on this variable. If you increase this by 1, then
   the size of the indexfile changes by: sizeof (int) * 1 * number-of-tickets.

   The maximum size of the index file is roughly 2MB for 30,000 entries with
   the default values. (MAXTKT * sizeof(index_entry)).

9. You can add more jokes or phrases to 'cookie-jar'.

10. Update 'initials' file with usernames and max 3 letter initials.

-------