Are there any limitations to making one machine the Submit Host for many jobs? Obviously jobdonecommands would be a factor, but outside of that, are there any limitations for one machine acting as the Submit Host for 100s of jobs?
On Mar 6, 2012, at 9:13 AM, Greg Ercolano wrote:
[posted to rush.general]
On 03/06/12 08:15, Gary Jaeger wrote:
> [posted to rush.general]
>
> If an artist submits a job, then shuts off his machine, does the job =
> continue to run? sorry not in front of a system to test and can't =
> remember the answer. thanks.
Depends.
The default behavior is the machine you submit from becomes
the job manager for the job, so in such a case you would not
want to shut the workstation off or have it go to sleep, otherwise
the job will be in limbo until the machine is running again.
The default use of the workstation ensures job management
is distributed among several machines, and not focused at one box.
However, if you don't want to use the local workstation as a job manager
(expect to shut it off, go to sleep, box is unstable, etc), you can
set the "Submit Host:" field in the submit form to the hostname
of some other machine to use as the job manager.
In that case, when you submit the job, that machine becomes
the job manager, and you can shut the local workstation down
without affecting the job.
The sysadmin can configure the submit scripts to force all
jobs to submit to a particular box by pre-loading the Submit Host
field with a specific hostname or set of hostnames.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|