The PBS TCL scheduler include in this directory was contributed by

	Amos Gouaux
	University of Texas at Dallas


PBS at the University of Texas at Dallas supports a Sun Ultra Enterprise 6000
running Solaris.  A brief reference can be found at
	http://www.utdallas.edu/utdgeneral/ir/unix/6000/
You may find this scheduler of interest.  The "policy" is described:


    Based on past experience, when we got this big E6000, we were
    concerned the CPU time not be wasted on things that can easily be
    done elsewhere.  So we decided to make the machine strictly a
    non-interactive batch system.  However, we realized that there would
    be times when interactive jobs might be necessary.
    
    So, the scheduler by default does not permit interactive jobs.  It
    also does not run non-interactive jobs if the load is over 40 (number
    picked because all the CPUs were just barely at 100% utilization when
    the load ave reached 40).  If someone presents a valid reason for
    interactive job use, we put their name in the  "intrctv.allow"
    file.  If the entry is just
    
       user=
    
    then the person has unlimited interactive job use.  If the entry is
    like this
    
       user=3:00:00
    
    then the user is allowed to have an interactive job for at most 3hrs.
    The scheduler sets the time limit resource of the job to this value.
    
    Interactive jobs by authorized users are allowed so long as the load
    average is below 20. When an interactive job is started, it is given
    a nice value of 19.  On a lightly loaded system, this won't really
    effect things. However if the machine is very busy, this nice value
    will mean the interactive jobs is rather pokey, which is one way to
    encourage folks not to do interactive work at that moment. 
    
    To clean up their job diskspace, the "job" partition is exported to
    only one machine -- the machine they are allowed to submit jobs from.
    So this smaller machine is used as a front-end to the batch machine.
    
    The mem max resource is set to 100mb, but only if the users have not
    specified a value.  This was done to get folks in the habit of planning
    how much mem they are going to need.  This is so that in the future I
    can add code to the scheduler to hold jobs if there's not enough
    memory to allow the job to run.
    


This code is neither supported nor endorsed by NASA Ames Research Center.
It is included with permission of the author as a sample of a working
scheduler for reference purposes.  The PBS developers would like to extend
sincere thanks to Amos Gouaux for allowing us to include his work in our
distribution.
