Additional Installation Notes
=============================

General Notes
=============

Most of the scripts should be modified to match your local configuration.
It may be worthwhile to create a centralized set of authorization files,
to be used with the 'do' operations in each script, so that you can easily
modify usernames and passwords without later interfering with the actual
data.

Web Installation
================

The following instructions assume a fairly basic Apache configuration; it
may not work with yours, but it has been known to work, and it's a good
start in setting up your own configuration.  Set up your files as so:

BASEDIR/
  SuperComp/
    stylesheet.css	Copied or linked from cgi-bin/stylesheet.css
    sc-times.cgi	Copied or linked from cgi-bin/supercomp/sc-times.cgi
    input		Generate this yourself (example files included)
  SysLoads/
    stylesheet.css	Copied or linked from cgi-bin/stylesheet.css
    sysload.cgi		Copied or linked from cgi-bin/sysloads/sysload.cgi
    input		Generate this yourself (example files included)
  Admin/
    .htpasswd		Created with 'htpasswd'  
    .htgroup 		See sample/htgroup-base
    .htaccess		See sample/htaccess-base
    stylesheet.css	Copied or linked from cgi-bin/stylesheet.css
    index.cgi		Copied or linked from cgi-bin/sysload_admin.cgi

Non-Web Installation
====================

The 'scstatus' script should probably be kept out of the main system
locations, and only used by whatever users and cronjobs need to populate
the SuperComp database.  Relevant cron entries:

  # Mail a weekly supercomputing status report.
  1 0 * * 0 /home/tskirvin/progs/bin/scstatus 2> /dev/null | /usr/bin/mailx -s "Supercomputer Usage Stats `/usr/bin/date`"  [email addresses] 

  # Get SC status information nightly for the databases.
  15 0 * * * /home/tskirvin/progs/bin/scstatus -d -q 2> /dev/null
  
'add-sysload' is expected to be in /usr/local/bin by the sysload package.
It is also run by the sysload package, so there's no need to worry about
crontabs.
