From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: Bug with jobdonecommand/dump?
   Date: Thu, 09 Dec 2010 15:55:57 -0500
Msg# 1976
View Complete Thread (6 articles) | All Threads
Last Next
Andrew Kingston wrote:
>>> That would be a good solution, I think.
>> 	Done; I've added this to 102.42a10.
>>
>> 	I've currently implemented it as optional flags to the jobdonecommand,
>> 	similar to the current '-nolog' flag, eg:
>>
>> 		-done     -- run only if all frames are 'Done'
>> 		-donefail -- run only if all frames are either 'Done or Fail'
>> 		-fail     -- run only if /any/ frames are 'Fail'
>> 		-always   -- run the command under any condition, even if frames
>> 		             aren't finished (ie. when job dumped mid-render)
>>
>> 	Abraham, at some point I can supply you with binaries for this new
>> 	version after I run some tests.
>>
> I'm running 102.42a9, but I really need the "-done" option on my job 
> servers.  Is it possible to just upgrade certain machines to 102.42a10?

	a10 hasn't been released yet.

	Note that you can get this already if you have your current
	donecommand script check the status of the job to see if it's
	Done or has Fail frames.

	When your donecommand runs, it will have various environment variables
	set telling you e.g. what the jobid is ($RUSH_JOBID).

	You can, for instance, use 'rush -lfi <JOBID>', or 'rush -lj <JOBID>',
	or you can look at the 'framelist' or 'jobinfo' files in the log directory
	to determine if the job completed with Done or Fail.


-- 
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)

Last Next