On Mon, 02 May 2005 13:32:18 +0200Alvar Freude <alvar@a-blast.org> wrote:
>Hi,
>
>-- Dennis Bjorklund <db@zigo.dhs.org> wrote:
>
>> The tcp hackers have provided an api for clients to set
>these values per
>> socket (setsockopt with TCP_KEEPIDLE and similar (in
>linux at least)).
>
>you can use SO_KEEPALIVE:
>
> [...] SO_KEEPALIVE enables
> the periodic transmission of messages on a connected
socket. Should the
> connected party fail to respond to these messages, the
connection is con-
> sidered broken and processes using the socket are
notified via a SIGPIPE
> signal when attempting to send data.
>
>
>For me it seems to be a good idea to support this. For the
applications
>(server, client) it is transparent, but notices a cutted
or broken network
>connection faster then before...
>
>But even with this you only realise that the connection is
>gone when sending something, AFAIK.
So this means, If client does never try to send data the
resources would be going to be held.
I think it is not a good solution to find zombie / dead
connection and clear them..
Best Regards,
Adnan DURSUN
ASRIN Bilişim Hiz.Ltd.
