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 sales@march-hare.com.
Thanks for the hint, however, I can't seem to get timestamps out. I've gone to the control panel, and enabled "Allow clients to trace server". I've then restarted the CVS service & lock service, and issues a cvs -ttt edit ReadMe.txt command, and see a bunch of debug trace information printed out, but no timestamps anywhere. Is there an additional option I need to set somewhere to see these timestamps? With some further testing, I've also noticed that my original Respository responds quickly - it is my newly added respository that is quite slow. I've checked the ACL permissions on both and they are the same. I've also compared the cvs trace of both, and noticed a slight difference: The slower repository has the following lines in the trace that the first one doesn't: S -> ParseInfo(D:/CVS/Repository/Medix/CVSROOT/precommand, /Medix, ALL) S -> ParseInfo(D:/CVS/Repository/Medix/CVSROOT/triggers, /Medix, ALL) ..... S -> ACL lookup on directory D:/CVS/Repository/Medix/impacttest/asp/impacttest S -> verify_acl(read,HEAD,(null)) ..... Any insight would be greatly appreciated! Thanks! Eric "Nicolas Courtiller" <ncourtiller at sgcc.com> wrote in message news:mailman.3.1131530732.17086.cvsnt at cvsnt.org... > Hi, > > Enable the trace mode on server side via the control panel, and then do > your > CVS action with trace flag to check what's occurs (look at timestamp). > For exemple: "cvs -ttt log ReadMe.txt". > > Hope this help. > Nicolas > > >> -----Message d'origine----- >> De : cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]De la part >> de Eric B. >> Envoyé : mardi 8 novembre 2005 19:43 >> À : cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook >> Objet : [cvsnt] Sudden slowdown with 2.0.62.1817 >> >> >> Hi, >> >> I've suddenly run into a strange problem and was hoping someone >> could point >> me in the right direction. I've been running 2.0.62.1817 for a good 6-8 >> months without problems until recently. >> >> Recently, I've noticed that any CVS action (ie: commits, edits, >> diffs, etc) >> all take a long time to process. Whereas these actions in the past would >> take a second or two, I am now seeing delays of 10-15 seconds on a single >> file commit! >> >> I've checked the server itself, and it seems clean. Have run >> spybot checks >> just in case, but haven't found anything suspicious. The machine in >> question is a Window 2000 SP3 machine. Also, the network connectivity >> between my machine and the server is fine as well - pings are >> fast, and any >> direct copying to shared folders on the server are quick. >> >> I can't pinpoint exactly when this slowdown occured, however the only >> changes I've made to the system in the recent past was the >> addition of extra >> repositories. I would not expect that to cause an issue, however, is it >> possible that a malconfigured repository would be causing such a >> slowdown? >> >> Is there any way to turn on some form of debug log or something >> of the sort >> to help me trace where / why this machine has suddenly slowed so much? >> >> Any insight that you can provide would be greatly appreciated! >> >> Thanks! >> >> Eric >> >> >> _______________________________________________ >> cvsnt mailing list >> cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook >> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs >> >