After playing with this a bit, I think this has done it. The question
now is, I'm seeing this with even some small networks. I tried
setting the buffer to just 64K, and didn't see the problem. So are we
going to have to tell everybody using UN*X to set this environment
variable or should this just be set in the dx script?
David
David, I think I chased this one down. Here's a note from the archives...
give it a try.
Greg
I've recently run down a problem that can cause a hang when you try to
execute extremely large networks that involves a deadlock situation in the
socket communication between the exec and the UI. To get around it I've
added an environment variable that allow you to specify a larger socket
buffer size (if the setsockopt call is available), named DX_SOCKET_BUFSIZE.
The value assigned to it is passed as the parameter to setsockopt for
SOL_SNDBUF and SOL_RCVBUF. I think the default is 32767, and the range is
clamped to the max allowed by the system. The value used is clamped to
the max allowed by the system; see your sysadmin if you need up this. I'm
using 262144.
Greg
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
