On Sun, July 16, 2006 20:14, Dylan Penhale wrote:
> Yes most of the PC's have 2 rushd.exe running all of the time, yet appear
> rush appears to be running ok. When you start rush there is one, as soon
> as a render starts the second appears and stays.
That should actually be OK -- that's just the parent to the renderer.
> The errors appear to be this:
>
> udp: udp.Receive(): recvfrom(): (10054) (WSA) Connection reset by peer
> udp: udp.Receive(): recvfrom(): (10054) (WSA) Connection reset by peer
> etc...
That would mean the daemon was busy doing something else when a UDP message
was sent to the daemon, and by the time the daemon got around to responding,
the program that sent the message went away (ie. someone didn't wait for
the response
and hit ^C, or the program 'timed out' and exited)
I would think there would be other messages that would cause the above.
Send me the /complete/ rushd.log that includes those messages. Send that
to my private email, and I'll respond here with specifics.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
** NOTE:
** I will be on vacation July 11th through July 20th.
** During that time, orders & email response may take over 24 hours.
**
|