Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Hey, I've got a similar problem to the one reported on this list a month ago but I didn't see a solution to it. I haven't had luck running the process as an Administrator instead of System like that person did. Basically every cvs command has about a 2:15 minute delay before there is a response. I've got "Don't resolve client names" checked and there is no anti-virus running. This is on a brand new virtual server that we just configured. Here is the output from cvs -ttt rls. Note that after hitting enter it took 2:15 for the first log message to appear and then again another pause you see in the log messages. All other messages finished within 1 second. Any ideas what is causing this? Thanks. C:\Program Files\CVSNT>cvs -d :pserver:user at 192.168.151.10:8081/cvsrepo -ttt rls 12:39:30: -> Tracelevel set to 3. PID is 2164 12:39:30: -> Session ID is 8744a1c1b426ad5 12:39:30: -> Session time is Tue May 26 16:39:30 2009 12:39:30: -> Client was compiled Nov 3 2008 23:29:25 12:39:30: -> Client was compiled with MSVC C/C++ 1310 12:39:30: -> Client build platform is microsoft-windows-x86 12:39:30: -> Client running on "Windows Server "Longhorn" Server 4.0 Service Pack 1 (Build 6001) [6.0.6001] (Service Pack 1)" 12:39:30: -> Loading protocol pserver as pserver.dll 12:39:30: -> CLibraryAccess::Load loading C:\PROGRA~1\CVSNT/protocols/pserver.dll 12:39:30: -> main loop with CVSROOT=: pserver:user at 192.168.151.10:8081/cvsrepo 12:39:30: -> start_server(0) 12:39:30: -> client start - client_protocol->connect 12:39:30: -> client start - Loop, getting responses from the server. 12:41:46: -> client start - got "I LOVE YOU" 12:41:46: -> client start - continue login. 12:41:46: -> client start - server started. -- Joe