[CF-Devel] Still getting errors

[Michael Toennies]

>
     
      I updated today 10-Jan-2001 and I am still getting these errors in my
     
     >
     
      /tmp/crosservlog
     
     >
     
     
     >
     
      ReadPacket got error 54, returning 0
     
     >
     
      CS: connection from client of type  CF DX CLIENT
     
     >
     
      ReadPacket got an error.: Connection reset by peer
     
     >
     
      ReadPacket got error 54, returning 0
     
     >
     
     
     >
     
      Any ideas?
     
     
Bob, this is normal and not a bug.

The DX client get the server data from the meta server.

Then it starts connecting to all server, get/send a version cmd, use the
time
the server needs to answer as latency (so the user can see how good his
connect to
this special server is) and then the client close the socket before login to
the server.

Then he connect to the next server in list, until end then he starts again.

Because there is no "logout" command, the server don't know what happened:
- has the client disconnected for some reason (= no error)
- or has the socket broken (= error)

So, when the client disconnect, the server don't no it and try to recieve
more data.
Then the recv() function (socket read function) notice that the socket is
closed, it breaks
and send this error number to the server. The server say: "Oh, client is
away" and do a
(normal and legal) shutdown of this socket. But because the recv() has send
the error message,
the server announce this to you, because the server don't know the reason
why the
client close the socket.