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.8 required=5.0 tests=BAYES_00,URI_HEX autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c22949b5ebf3505f X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-05-08 14:49:05 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!fu-berlin.de!uni-berlin.de!212.97.175.23!not-for-mail From: Jano Newsgroups: comp.lang.ada Subject: Re: [OT] Two sockets questions Date: Thu, 8 May 2003 23:48:48 +0200 Message-ID: References: <8765omaa6b.fsf@inf.enst.fr> <87smrpe0uo.fsf@inf.enst.fr> NNTP-Posting-Host: 212.97.175.23 X-Trace: fu-berlin.de 1052430542 19705731 212.97.175.23 (16 [49872]) X-Newsreader: MicroPlanet Gravity v2.50 Xref: archiver1.google.com comp.lang.ada:37084 Date: 2003-05-08T23:48:48+02:00 List-Id: In a side note, trying to do the "select" trick proposed yesterday to see if the connection is alive, I've found that the Gnat implementation has a side effect. It clearly specifies that a special descriptor is opened with each select_type to allow the abortion of a select. However, when you closes the select_type, that descriptor is in TIME_WAIT status (normal, I suppose). As my "bright" idea was to create a select_type, select on the supplied socket to be tested with immediate time out, and close the selector afterwards, that implies that for every test you get a TIME_WAIT. Doing the test quite frequently (I was in my test doing it once a second or more!) leaves you quickly with a loooong list of descriptors in TIME_WAIT status. FWIW. -- ------------------------- Jano 402450.at.cepsz.unizar.es -------------------------