Very Computer

Hi,

Here is what happened.

I use tcp for both server and client connection.

If I close server socker first before all clients close their socket, I will
get
"error in bind 98" tcp socket when I connect with same tcp port again.

Is there any way that I avoid this problem?

I am working on peer to peer network game. One of the player machine is set
to server.
I hope I can close server socket first. And all other clients just get tcp
connection close then close their own socket.

Otherwise, the server has to wait all clients to close. I don't want that
server player machine waits for others.

thank you.

steve

Hi,

Here is what happened.

I use tcp for both server and client connection.

If I close server socker first before all clients close their socket, I will
get
"error in bind 98" tcp socket when I connect with same tcp port again.

Is there any way that I avoid this problem?

I am working on peer to peer network game. One of the player machine is set
to server.
I hope I can close server socket first. And all other clients just get tcp
connection close then close their own socket.

Otherwise, the server has to wait all clients to close. I don't want that
server player machine waits for others.

thank you.

steve

On my Linux box, error 98 is EADDRINUSE (Address already in use),
which makes sense.  But you probably want to use the strerror function
to get a human readable text for the errno value.

Quote:> Is there any way that I avoid this problem?

man setsockopt and read about SO_REUSEADDR.

Quote:> I am working on peer to peer network game. One of the player machine is set
> to server.
> I hope I can close server socket first. And all other clients just get tcp
> connection close then close their own socket.

> Otherwise, the server has to wait all clients to close. I don't want that
> server player machine waits for others.

--

Nate Eldredge