Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 25 Jan 2002 10:59:55 +0100 From: Corinna Vinschen To: "Pierre A. Humblet" Cc: cygwin Subject: Re: socket/fdopen/exec problem Message-ID: <20020125105955.P11608@cygbert.vinschen.de> Mail-Followup-To: "Pierre A. Humblet" , cygwin References: <3C50520B.3239FAC5@ieee.org> <20020124220339.K11608@cygbert.vinschen.de> <3C5080F8.4E4B8945@ieee.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C5080F8.4E4B8945@ieee.org> User-Agent: Mutt/1.3.22.1i On Thu, Jan 24, 2002 at 04:47:36PM -0500, Pierre A. Humblet wrote: > Corinna Vinschen wrote: > > > Isn't that just the usual effect that sockets remain in TIME_WAIT > > state for 2MSL seconds? > > I realize I am mixing two things. Seeing reused ports in netstat > isn't much of a problem in itself, as long as new calls can come > in. That's the OK case I see now all the time on NT. However the > problem I am chasing (on Win98) is that new calls are not accepted. Did you set the SO_REUSEADDR flag? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/