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
--On July 21, 2003 05:28:29 PM <[EMAIL PROTECTED]> wrote:
Look at the script /usr/local/bin/dx and edit the script around line 464
and remove the line that sets the DX_SOCKET_BUFSIZE or you can replace it
with the following:
if [ -z "$DX_SOCKET_BUFSIZE" ]; then
DX_SOCKET_BUFSIZE=262144
export DX_SOCKET_BUFSIZE
fi
Nomatter if you set DX_SOCKET_BUFSIZE or not, your changes probably don't
change it since I accidentally hardcoded it in there. Then you can try
setting it to numbers yourself.
David
Thanks for the advice. I increased the system limit and set the DX env
variable as suggested but still see two errors of the form
SOCKET bufsize mismatch: xxx buffer (yyy zzz)
where xxx is rcv or send, and the various values of "yyy zzz" depend
upon the env variable as follows:
DX_SOCKET_BUFSIZE ===> yyy zzz
not set ===> 262144 524288
524288 ===> 524288 1048576
1048576 ===> 1048576 2097152
Have 512MB on this system but don't want it all going to buffers!
Suggestions? Kent
