Gary Jaeger wrote:
> [posted to rush.general]
>
> I'm curious how people manage the log files. For instance say we have a =
> maya scene with lots of render layers. And if we want to submit =
> different jobs for each render layer, then specifying different =
> directories for logs gets to be a pain.
BTW, I have an offline version of submit-maya that lets you
specify multiple layers and frame ranges for each, so that
you can submit a multi-layer, multi-frame-range job in a
single submission/single job.
It will be part of the new submit-maya script in the next release.
I'll email it to you offline.
Anyone else interested in testing that, feel free to contact me
directly, and I'll provide it to you.
> I wish we could specify some =
> sort of variable like <JobID> so that rush made a new directory every =
> time we did a submit with a unique ID. Then we could have a =
> /logs/<JobID> for each job. Would that make sense?
There is such a thing; if you specify a '%s' on the end
of the log directory pathname, rush will automatically stick
the jobid on the end, and will automatically make the directory. eg:
http://www.seriss.com/rush-current/rush/rush-submit-cmds.html#LogDir
So for instance, in the submit-maya form, under the Rush tab
if you specify:
Log Directory: /some/path/myscene/logs/%s
..that will create a subdir in the 'logs' directory named after the
job's jobid, and will use that as the log directory.
You might want to have a cron job clean that dir out of dirs older
than a week or so. Or you can configure the job's 'jobdumpcommand'
to remove it for you; I leave it to my customers to construct
the correct 'rm -rf' command to clean out the production dirs..
too scary for me ;)
--
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)
|