I would tend to guess your box is acting as the submit server? Meaning
your machine is controlling your job. I would recommend setting up a
couple submit servers that never reboot and are up all the time. You
submit your job to eb rendered to these servers, so if your boxes
crashes.. rebooted.. whatever you are not affected. To me this is the
typical setup for a render farm....
or maybe I am miss reading the e-mail
-Saker
Christopher Janney wrote:
[posted to rush.general]
We have dual boot win/linux boxes here. Since we work primarily in
windows, we do not have rush.d running on the linux side, and I don't
think it would even help in this case.
When we submit a job on the windows side, then boot into linux, the
frames that are already rendering continue to do so, but the rest of
the job is basically paused until that workstations rush.d is started
again. This means if that machine crashed in the night, no render in
the morning, etc. There has got to be a way around this.
Thanks!
-ctj
Christopher Janney
www.a52.com
|