I did some more experimenting and found the problem with quick restarts and port bind errors! But not the solution :)
The printing of a "." may lessen the chances of this or have nothing to do with it. The real problem is in the following: dev5# netstat | grep 8092 tcp4 0 0 localhost.8092 localhost.4213 TIME_WAIT tcp4 0 0 localhost.4212 localhost.8092 TIME_WAIT tcp4 0 0 localhost.8092 *.* LISTEN tcp4 0 0 localhost.4209 localhost.8092 TIME_WAIT tcp4 0 0 localhost.4207 localhost.8092 TIME_WAIT I refreshed a browser page a few times to create those sockets. The only one that will cause a bind problem on restart is this one: tcp4 0 0 localhost.8092 localhost.4213 TIME_WAIT For some reason, webkit owns the connection to the adaptor instead of the other way around (notice which side the 8092 is on). I use 8092 instead of the default 8086 for this instance of webkit.. So, to fix the problem we need to figure out why this socket is backwards. Any ideas? Jeff _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
