Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: setsockopt SO_REUSEADDR Date: Tue, 5 Oct 2004 15:43:33 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <58650.193.16.155.145.1096986545.squirrel@193.16.155.145> Message-ID: X-OriginalArrivalTime: 05 Oct 2004 14:43:33.0564 (UTC) FILETIME=[B05467C0:01C4AAE9] > -----Original Message----- > From: cygwin-owner On Behalf Of Rainer Hochreiter > Sent: 05 October 2004 15:29 > running the program listed below with argument 'reuse' under > cygwin and linux returns different results! > > from my point of view, the linux result is quite what i > expected, a bind() error 'Address already in use'. Huh? But that's exactly what SO_REUSEADDR is supposed to _prevent_ from happening. That's why it's called _REUSE_addr, because it lets you *re-use* an addr, without getting an error message. Why would you expect setting it to stop you from reusing the address? > why doen't bind() return an error under cygwin? Because SO_REUSEADDR works _correctly_ on cygwin, perhaps? cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/