Teemu <teemu@easy.com> wrote:
> The behaviour seems to be different in different cases. If the the
> client the connection breaks because software-hangs etc. The error
> is given right away. However if the connection is lost because the
> network is down such as in the case that I cut the cable etc. then
> it does seem that if I use for instance 4k buffer size and keep
> sending pakcets it takes very long to get anykind of notification
> that the connection is lost.

Indeed if the remote app goes toast, a send to it will elicit a RST as
the remote TCP is still running. The remote system goes toast, and
packets go into a black hole. No RST and you have to wait for the
retransmission timeouts.

However, I'd be very surprised if the retransmission timeouts were
affected by the settting of SO_SNDBUF.

They would be affected by system tuning - say via sysctl.

> I'm hoping to get either one of those messages, but basically any
> error would do. Also because of serious threading the errno is
> sometimes changed before I have time to read it..

Huh? I was under the impression a properly threaded situation would
have a thread-specific errno. Are you sure that you are running on
"proper" threads and have compiled "properly" for threads on yhour
platform?

rick jones
--
Process shall set you free from the need for rational thought.
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to raj in cup.hp.com but NOT BOTH...