From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: when the submitting workstation dies, so does the render
   Date: Fri, 13 Oct 2006 17:27:03 -0400

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.

	If I follow correctly, you just want to be able to requeue
	the frames that were running on the box at the time you shut it down?
	ie. after you requeue the frames, they remain in the 'Die' state
	because rush is unable to get a confirmation the render was killed
	because the box is down or dual-booted.

	Simple answer: use the 'Down' button in the irush "Frames" report
	to tell rush that machine is down. Right click on the 'Down'
	button in irush "Frames" report for help.

	Or, from the command line you can use the 'rush -down' command as well:
	http://www.seriss.com/rush-current/rush/rush-command-line-options.html#-down

	Rush does not automatically assume a machine is down if it hasn't
	responded for a while, because often that situation just means the
	machine is under a lot of load (thrashing). It's worse for rush to
	assume a machine is down, when it really is not, as then you get the
	worse situation where more than one machine is working on the same frame,
	the separate machines overwriting each other's work.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)