Just tried setting the buffer size to 131070; the warning says that is what
it requested but double that is what it got. I still have the setting of
the socket size in /usr/local/dx/bin/dx commented out. Since this is just a
warning, I could just ignore it for now.Should we leave it at that?
Kent
--On July 22, 2003 11:56:19 AM <[EMAIL PROTECTED]> wrote:
Its not actually an error, it is more a warning. But I don't understand
where it could be coming up with the doubling affect. It is using
setsockopt to increase the bufsize and then rereads what the system
actually set with getsockopt and compares the two. Have you tried setting
it lower, say 131071?
The system default for many Linuxes is 65535, but this may be too low and
is exhibited by a dead lock condition when loading some large networks.
David
Thanks, David. In /usr/local/dx/bin/dx, around line 464, the script
already reads as you suggest (below). Do I have the wrong version?
As a test, I commented out the code you show below and dx ran with
no errors. Then I repeated the test but with DX_SOCKET_BUFSIZE set
to 500000; then, the error returns with yyy zzz ===> 500000 1000000.
It looks like DX is always obtaining a buffer twice the size it
wants except when using defaults.
Kent
--
.........................................................................
.... David L. Thompson Visualization and Imagery
Solutions, Inc. mailto:[EMAIL PROTECTED] 5515 Skyway Drive,
Missoula, MT 59804 Phone :
(406)756-7472
- - -
Kent Eschenberg [EMAIL PROTECTED] (412)268-6829
Scientific Visualization Specialist, Pittsburgh Supercomputing Center
There are 10 types of people in the world: those who
understand binary, and those who don't.
