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 email@example.com.
Hi Tony Today I had so many problems with LockServer that I had to disable it. My configuration is: cvsnt 2.0.26 pserver and sspi clients Windows 2003 Server 2x933 MHz P3 512 MB RAM repository with 30000 files in 6000 dirs - total 1.4 GB No AV software Before disabling the lockserver, I twice saw the following: Lockserver using 100% on one cpu, about 10 cvs.exe processes howering on 1-2% of the other and just about no progress. Actually i think that there was no progress for some of the clients, but thats hard to be certain about. I rebooted the server, and for a while everything went fine, and then lockserver locked up (pun intended) once again. What should i look for? The number of locks? And what would cause a high number of locks? Should i run lockserver -test and what should i look for in the output? Best regards /MJ "Tony Hoyle" <tmh at nodomain.org> wrote in message news:hiik20hccq872j2pu91rqpgdq1dn28ec7a at 4ax.com... > On Wed, 11 Feb 2004 16:20:16 +0100, "Morten Joehnk" <no at mail.for.me> > wrote: > > >Just installed CVSNT 2.0.26 and we are now for the first time using > >lockserver. It seems that the lockserver process has a very high CPU load > >(around 60%) and slows the machine down quite a lot. > > > I've never seen the lockserver get above 1% of network load.. it > doesn't really do anything - it keeps a list in memory of active locks > and deletes them when they're finished. The only time you'd get any > kind of CPU spike is if you have many thousands of locks in operation > simultaneously, which generally doesn't happen. > > Try telnetting into it (port 2402), type 'monitor', then usr the > 'clients' and 'locks' commands to see what's active. > > Tony >