Gary Jaeger wrote:
This may qualify as a "d'oh!" but I'm just now discovering that the
machine which submits a job must stay online? Is that correct?
By default, the machine you submit from becomes the job server
for that job.
So yes, if you shut off the machine acting as the job server
for your job, then the job will stop until you get it back up
at which point it will pick up where it left off.
But you can also tell rush which machine(s) to use as the job server(s)
for your jobs using the 'Submit Hosts' prompt. In most modern rush
submit scripts, under the 'Rush' tab there's a 'Submit Hosts:' prompt
where you can enter the names of hosts to use as job servers.
When there's more than one, the submit script will pick one at
random, so that your jobs can be distributed across several machines
(instead of throwing them all at one box)
As the sysadmin, if you have say 3 machines set up to be job servers,
then you can modify the submit scripts so that the 'Submit Hosts'
prompt is set to those three hostnames.. then all users will have
their jobs managed by those three machines.
On large networks, it's best to have more than one server, so that
the load of job management is distributed across several machines
rather than all focused at just one box.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|