> Is there a way to stop all rush rendering?
>
> Sometimes our file server gets full, and we want to be able
> to stop everything before it gets too full..
Yes, if you want to stop all renders on the network..
STOP EVERYTHING IMMEDIATELY
---------------------------
If you want everything to stop RIGHT NOW, killing renders
that are in progress (and re-queing them) so that NOTHING
is left running, your can use:
rush -getoff +any -t 3
This is the same as 'offline', just the added function of
killing and re-queuing anything that is currently running
so that it will be re-started later.
More info:
http://www.seriss.com/rush-current/rush/rush-command-line-options.html#-getoff
STOP ONLY NEW RENDERS FROM STARTING
-----------------------------------
If you don't want to KILL renders that are running, but want
to 'gracefully' just prevent new frames from starting, you
can just use:
rush -offline +any -t 3
As currently rendering frames finish rendering, no new frames
will start, easing everything down to a graceful stop.
More info:
http://www.seriss.com/rush-current/rush/rush-command-line-options.html#-offline
TURNING EVERYTHING BACK ON
--------------------------
After one of the above global "getoff" or "offline" operations
is run, you can bring everything back on again via:
rush -online +any -t 3
..this will re-enable the machines to accept renders and
start frames running. Any frames that *were* running (and were killed)
will be restarted.
More info:
http://www.seriss.com/rush-current/rush/rush-command-line-options.html#-online
* * *
In all the above cases, the '-t 3' flag sets a 3 second limit for
how long to wait for unresponsive machines. If unspecified, it will
wait 45 seconds, which is a long time to wait if one of the machines
is turned off. You can change the '-t 3' to a larger or smaller number,
depending on how long you're willing to wait for unresponsive machines.
Security Note: you can use the rush.conf file to control which users
are allowed to run these commands; see:
http://www.seriss.com/rush-current/rush/rush-conf.html#Permit
|