Robert Minsk wrote:
> [..] If you do this I would recommend printing the users environment
> as the last step before running your render command so you will have a copy
> in the rush log file. This is very useful for looking at what could be
> causing a failure for a user.
Right; I believe most of the submit scripts have an option for this:
Print Environment? on/off
..which is by default 'off'. You'll find this option if you
scroll down to the very bottom of the 'Rush' tab in the submit
script's input form.
Turning this 'on' executes a 'printenv' (unix) or 'set' (windows)
just before the render runs, so you can see what the environment
settings are within the frame logs for debugging.
Or, you can jam a system("printenv") command into the perl script
where ever you want to print the environment, eg:
# SHOW ENVIRONMENT, WHETHER WINDOWS OR UNIX
system($G::iswindows ? "set" : "printenv|sort");
..or even:
# SHOW ENVIRONMENT
foreach (sort(keys(%ENV))) { print "$_=$ENV{$_}\n"; }
..which is pretty much the equivalent 'pure perl' way to print
the environment.
|