[CF-Devel] Bug in cvs checkout on 09-Jan-2001?

[Michael Toennies]

>
     
      > Upgraded to the latest cvs snapshot and I am getting these message in my
     
     >
     
      > /tmp/crossvlog files:
     
     >
     
      >
     
     >
     
      > Waiting for connections...
     
     >
     
      > ReadPacket got an error.: Connection reset by peer
     
     >
     
      > ReadPacket got error 54, returning 0
     
     >
     
      > CS: connection from client of type  CF DX CLIENT
     
     >
     
      > Waiting for connections...
     
     >
     
     
     >
     
       My understanding is that the DX client does a
     
     >
     
      connection/disconnect to the
     
     >
     
      servers to find out relative latency, so those messages are harmless.
     
     
Thats right, i just connect to the server, send/get version cmd and use the
time
the server needed to answer as latency and disconnect then.

The error comes because there is no "bye" or "logout" cmd. The server can't
determinate the difference between a broken connect or a client side closed
connect.

Perhaps we should add a quick "bye" cmd, so the server can handle it in the
right?
It works so fine, but its a somewhat dirty way.

Also, iam not sure that the way i connect direct to the server is a good way
to
get the latency. The idea is of course to get the time the server really
need to
serve a single user. But when we have many users, the server can get dozens
of these
"ping connects" per seconds. I have no idea about th effects on server speed
or
connections.

Any ideas what happens then or will it a bad attack to server performance?

A normal ping will also work, but only show you the connect to the used
server,
not the real cf speed. And this can change when much user are online or the
server thread runs with low priority.