TDS version 0.4
===============
There are 2 parts to the application: the daemon and the GUI.


Simple Install (4 steps)
==============

1. Download and, as root, unpack the gzipped tarball (tdsnn.tgz, where nn = version)
   into "/", which will create /tds, subdirectories, and supply the required
   program files.

2. Add the following lines to your login script (e.g. .bashrc):

TDSDIR=/tds
export TDSDIR

3. Activate the daemon:

/tds/tdsd > /tds/tdsd.log 2>&1

4. Activate the GUI:

/tds/tds &

(the GUI's Monitor display refreshes automatically every 15 seconds)


Source Install
==============
Download and unpack the gzipped tarball (tdssrcnn.tgz, where nn = version) into
the directory of your choice. The /tgsd subdirectory contains the daemon source,
and the /tdsg subdirectory contains the GUI source tree.

Source Build
============
"make all", in the /tdsd directory, builds the daemon.
Use KDevelop to build the GUI.
Copy tds, tdsd, tdscheckpoint, and xpm* to your tds base directory (TDSDIR).


Notes
=====
The application won't function properly unless the daemon is running.
For excessive debug information, define TDSDEBUG (and export it) prior to
running the daemon.  Make sure you read the 'FINALLY' note at the end of this
document.


TDS datafiles
=============
/tds               Base directory (TDSDIR) contains the programs and documentation
/tds/jobs          contain the job files
/tds/logs          contain the job logs
/tds/status        contain the job status files
/tds/groups        contain the group files

in each subdirectory, the name of the file corresponds to the name of the job.
The Job files (in /tds/jobs) are directly editable, and are composed thus:

script_name
user_name
pre-requiste_list

so, for example, a job called MYLASTJOB, activating a script called MYSCRIPT,
which runs under ROOT, having the pre-requisites MYFIRSTJOB and MYSECONDJOB,
would have a filename of MYLASTJOB, and look like this:

./MYSCRIPT
ROOT
MYFIRSTJOB
MYSECONDJOB

(note that there must be a CR/LF at the end of the line saying MYSECOND job,
and that uppercase words have been used only for emphasis)

The Group files (in /tds/groups) are also directly editable, and each file
contains a list of jobs - again, with a CF/LF at the end of each line.
Note that the GUI's Group Release function will release jobs in the same Group
*except* for jobs that are "on hold". This is deliberate application behavior.


FINALLY
=======
In order to use the application, you will need to define TDSDIR. This can
be achieved by adding the following lines to your login script (e.g. .bashrc):

TDSDIR=/tds
export TDSDIR

if TDSDIR is undefined, the GUI assumes /tds is the TDS base directory. Also, the
GUI expects to find the xpm files (e.g. xpmrunning) in the base directory.