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.
One strange thing about the problems we had: The LockServer would stay on with a high CPU usage even with no cvs.exe processes on the server. /MJ "Morten Joehnk" <me at no.mail.for.me> wrote in message news:c0tu5p$ria$1 at sisko.local.nodomain.org... > Great - I'll let you know what happens > > :-) > > /MJ > "Tony Hoyle" <tmh at nodomain.org> wrote in message > news:n7t430lk7124grdvfer2j4qdrqorrtcatl at 4ax.com... > > On Tue, 17 Feb 2004 21:08:40 +0100, "Morten Joehnk" > > <me at no.mail.for.me> wrote: > > > > >Thanks for your fast responses, Tony > > > > > >There were no commits running when we had the problems - only updates and > a > > >single checkout > > >I'll have to run it without lockserver for a couple of days, and when i > get > > >some time to test, i'll switch it back on and see if i can reproduce the > > >problem and then try monitoring it > > > > > Monitoring itself adds load (as it has to send extra data out to your > > client), so do any tests with it off and use that just when things > > look wrong. > > > > Testing the 2.0.26 lockserver vs. the 2.0.29 lockserver is worth a try > > too as it scales better in the later versions. > > > > Tony > > > >