|
|On Fri, July 14, 2006 02:59, Dylan Penhale wrote:
|> [posted to rush.general]
|>
|> We are running rush 102.42
|>
|> Can you tell me if the rush -ljf bug mentioned in the update details
|> for 102.42a6 applies to windows machines, and if the version we are
|> running should suffer from this bug?
|>
|> We are seeing more than one rushd.exe pretty much all the time on
|> windows hosts seemingly making them very slow to respond to iRush.
|
|The bug doesn't affect windows; it's unix only.
|
|There will be more than one rushd.exe process normally.. what would be
|abnormal is if the extra rushd stays running for longer than a few
|seconds.
|That means it's trying to access something it can't reach.
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.
|
|If you're having problems with slowness, check the rushd.log files for
|errors and include them here.
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...
|