RE: setsockopt SO_REUSEADDR

2004-10-06 Thread Rainer Hochreiter
On Tue, 05 Oct 2004 09:54:39 -0500, Brian Ford wrote: > BTW to the OP, why are you printing the address of the socket function > out? I think you meant to print "s" instead of "socket"? oops - you are right! i wanted to print the socket and not the address of the socket() function! ;-) rainer

Re: setsockopt SO_REUSEADDR

2004-10-05 Thread Brian Dessent
Warren Young wrote: > As I see it, the purpose of SO_REUSEADDR is to allow a program to bind > to a port that still has WAIT states on it. (FIN_WAIT_x, TIME_WAIT, That, and the part about the uniqueness of local IP+port. Think multihomed boxes that want to do ip-based virtual hosting. It seems

Re: setsockopt SO_REUSEADDR

2004-10-05 Thread Warren Young
Dave Korn wrote: Because SO_REUSEADDR works _correctly_ on cygwin, perhaps? Oh, I don't know about that. As I see it, the purpose of SO_REUSEADDR is to allow a program to bind to a port that still has WAIT states on it. (FIN_WAIT_x, TIME_WAIT, etc...see netstat(1) and the Stevens TCP/IP books.

Re: setsockopt SO_REUSEADDR

2004-10-05 Thread Corinna Vinschen
On Oct 5 09:54, Brian Ford wrote: > On Tue, 5 Oct 2004, Dave Korn wrote: > > > > -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 retur

RE: setsockopt SO_REUSEADDR

2004-10-05 Thread Brian Ford
On Tue, 5 Oct 2004, Dave Korn wrote: > > -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

RE: setsockopt SO_REUSEADDR

2004-10-05 Thread Dave Korn
> -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 b