From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,297123c81a4f80e1
X-Google-Attributes: gid103376,public
From: Laurent Guerby <guerby@acm.org>
Subject: Re: Socket buffer filling up
Date: 1999/11/19
Message-ID: <86aeoafdsq.fsf@ppp-162-48.villette.club-internet.fr>#1/1
X-Deja-AN: 550667566
References: <383403bd.0@silver.truman.edu> <383404ee.0@silver.truman.edu>
 <38342539.0@silver.truman.edu>
X-Trace: front6m.grolier.fr 943041643 6262 195.36.162.48 (19 Nov 1999 20:00:43
 GMT)
Organization: Club-Internet (France)
NNTP-Posting-Date: 19 Nov 1999 20:00:43 GMT
Newsgroups: comp.lang.ada
Date: 1999-11-19T20:00:43+00:00
List-Id: <comp.lang.ada>

"Chad R. Meiners" <v025@truman.edu> writes:
>     I believe your problem has to do with the fact you are only shutting
> down the socket and not closing it.  You are running out of available
> sockets so either you need to reuse the sockets you have, or you need to use
> the close_socket api form the Winsock api's to release them so other
> programs can allocate sockets.  I have extended Jerry's socket package to
> have this functionality.   E-mail me if you would like this package

I noticed the problem some time ago and notified the Unix and NT
maintainers, they both told me that it would be fixed in the next
release of adasocket.

On Unix, you need to call C_Close (which is in the thin binding),
and on NT as Chad mentionned.

BTW, while we have socket experts on line, I'd like to know if it is
possible to check that the peer on the socket is still here without
having to send data (and thus getting some kind of connection lost)?

Thanks for any insight,

--LG