Hi, Stupid question time: how does windows hand of something to the right server? I thought that the port/ip combination was supposed to be unique.
> [EMAIL PROTECTED] writes: > > > rbb 02/02/04 22:16:04 > > > > Modified: . STATUS > > server listen.c > > Log: > > This change keeps the server from allowing multiple instances to bind to > > the same port. Previously, this was necessary, because the Windows MPM > > was binding to the socket in both the parent and child. Today's code > > passes the attached socket to the child from the parent, so we don't need > > to re-attach in the child. > > what the *&%#... you broke everybody else (and perhaps Windows in > some scenarios) > > -1 > > This change also prevents a single instance (i.e., normal scenario) to > bind to the desired port when an old connection is in TIME_WAIT or some > other TCP state. > > I can't see any SO_REUSEADDR being done on Unix now and meanwhile I > have a continual stream of regression test failures saying: > > (98)Address already in use: make_sock: could not bind to address > 0.0.0.0:8099 > no listening sockets available, shutting down Very nice. Great for restarts... Not. Sander
