Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <432997BC.FDDB1882@dessent.net>
Date: Thu, 15 Sep 2005 08:48:12 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: help on socket connexion
References: <4a03a72c050914161345feff39 AT mail DOT gmail DOT com> 	 <20050915082911 DOT GU5555 AT calimero DOT vinschen DOT de> <4a03a72c05091508275f0c5bd2 AT mail DOT gmail DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

znort wrote:

> Ok, part of code...
> 
> If I run a client test (loop of 60 connection) to connect to the
> server, all the fork/connection are ok...
> but sometimes all the fork still "hang" in the process list even if I
> stop the client
> 
> (sorry but the code is "as is")

How can this code possibly compile?   There are no #includes!  When
someone asks for a testcase, that means something that will compile and
run -- not a snippet of something.

Before you continue, make sure your code compiles with no warnings with
-Wall.  If it does not, then fix the warnings.  They usually indicate
that you've done something wrong.

In general you can in fact define FD_SETSIZE to a larger number if you
desire, but this must be done BEFORE the system headers are included, so
that it is already set when the FD_ macros are defined.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/