From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: log directory
   Date: Mon, 09 Jul 2007 16:15:07 -0400
Msg# 1601
View Complete Thread (9 articles) | All Threads
Last Next
Kym Watts wrote:
> Hey,
> 
> We had fun working this out when we moved our logs to a standard location.
> As long as the base dir exists: 
> "//sledgehammer1/share/rush/farmlogs/$project/renders/"
> And then you use the "_%s" after say the jobname, it will create the log 
> folder. 
> [..]
>  LogDirectory: //sledgehammer1/share/rush/farmlogs/project/renders/testrender_%s

	Yes, the newer submit scripts will handle that %s correctly,
	replacing the %s with the jobid of the job, and creating the
	resulting directory automatically, so that the /jobid/ is encoded
	into the log directory's pathname.

	The %s thing is handled internally by Rush to avoid the catch-22
	situation where you can't know the jobid until you submit the job,
	but can't submit the job with the jobid in the path until you know
	the jobid. By handling this internally, Rush correctly times the
	creation of the pathname and directory.

	More info on the '%s' trick here:
	http://www.seriss.com/rush-current/rush/rush-submit-cmds.html#LogDir

	The %s trick works in most cases without any modification to the
	submit scripts, except in special cases where certain scripts try
	to save scene info into the log directory before the job is submitted.
	In that case the %s trick won't work, or has to be handled carefully.

	However, to get what Gary was requesting, where the scene filename
	gets inserted into the log directory as opposed to the jobid.. that
	code snippet I sent him should do the trick.

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

Last Next