Dylan Penhale wrote:
Recently we have been performing a roll out of 102.42.a6 to some (and
eventually all) of the machines on the network, starting with the XP
machines. I have noticed that when we offline rush and then net stop rushd
we sometimes get mayabatch coming back in the process tree.
Is there a reason you're not using 'rush -getoff' instead
of 'net stop rushd'?
'net stop rushd' is kind of harsh, as that will likely
orphan the renders.
If we kill it in
task manager it comes back up to three times in total.
Sounds like the retry loop from the script, which is probably
not being killed.
You want to kill both the script and the mayabatch, in that order.
several times. Your other email explained the rush process tree being:
111 rushd
\
112 perl /path/to/renderscript
\
113 maya -batch
So I can't really understand how these mayabatch processes could be coming
from rush once it is stopped unless something is miss-configured somewhere.
If you kill rushd, the perl script and maya -batch become orphaned.
If you then kill 'maya -batch' (or mayabatch), the script is still
running, and its retry loop will try to restart maya (up to three times)
Are you aware of anything else that could fire of these retries?
No, I'm pretty sure it's as I describe.
Keep in mind rushd is not responsible for the retries,
the perl render script is.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|