[cvsnt] CVSNT 2.5.04 build 3236 server really slow

[Arthur Barrett]

Yuda Sidi,

> This server is not connected to the internet.  The DNS is configured
> properly forward and reverse. 
>  
> "ping yahoo.com" returns with an error message after 3 seconds.
> "ping -a 199.7.71;190" returns from the reverse DNS after 5 seconds.

Then something is really really wrong with both your forward and reverse
DNS.

Please fix your DNS before proceeding any further.  PING time for yahoo
should be no more than 200ms:

$ ping yahoo.com

Pinging yahoo.com [68.180.206.184] with 32 bytes of data:

Reply from 68.180.206.184: bytes=32 time=149ms TTL=55
Reply from 68.180.206.184: bytes=32 time=168ms TTL=55
Reply from 68.180.206.184: bytes=32 time=142ms TTL=55
Reply from 68.180.206.184: bytes=32 time=176ms TTL=55

Ping statistics for 68.180.206.184:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 142ms, Maximum = 176ms, Average = 158ms


$ ping -a 68.180.206.184

Pinging w2.rc.vip.sp1.yahoo.com [68.180.206.184] with 32 bytes of data:

Reply from 68.180.206.184: bytes=32 time=186ms TTL=55
Reply from 68.180.206.184: bytes=32 time=168ms TTL=55
Reply from 68.180.206.184: bytes=32 time=168ms TTL=55
Reply from 68.180.206.184: bytes=32 time=169ms TTL=55

Ping statistics for 68.180.206.184:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 168ms, Maximum = 186ms, Average = 172ms


> When I  enter  "cvs" (without setting cvsroot) on the server no
> parameters it takes 15 seconds till the command is executed. 
> This means
> each cvs command will take at least 15 seconds to execute. 
>  
> Is there any possibility to speed things?

Read this thread all the way through to the end.  It contains
instructions how to diagnose the problem and also the most common reason
for the cause (DNS problems with verifying the signature on the EXE and
DLLs):
http://www.cvsnt.org/pipermail/cvsnt/2008-October/031355.html

At least one other person was not able to correctly configure their DNS
to get this to operate and we are working on a further update for people
thus affected.

Regards,


Arthur Barrett