[cvsnt] Dead cvs.exe processes

[David Jackman]

I actually was able to disable the AV checking, so we'll see if that has
any effect on things.

I may at some point have some spare time to set up scripts on the server
to trigger a build when a commit happens (but allowing for a quiet
period).  That won't be trivial, though.  And we will lose the ability
for CC to send emails to only those people that had commits involved
with the build, which isn't going to be popular.

So you're saying that most likely the 400+ cvs.exe processes I'm seeing
are all log processes that haven't finished yet?  Will the client
process finish and leave the server process still going?  That's the
only way it could get that many.  If the client side is still waiting
for the command to complete, then I should see at most 4 such processes
on the server (since that's the number of active threads on CC).

Also, I did a cvs log command on our largest project, and it completed
in just under 3 minutes (with 305 cvs.exe processes currently on the
server).  I shut down CC and waited 20 minutes, and only 2 of the 305
processes went away.

 

-----Original Message-----
From: Tony Hoyle [mailto:tony.hoyle at march-hare.com] 
Sent: Wednesday, January 25, 2006 12:26 PM
To: David Jackman
Cc: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Dead cvs.exe processes

David Jackman wrote:
> CruiseControl has been using cvs log for determining if a project has 
> been modified for as long as I can remember.
> (http://cruisecontrol.sourceforge.net/main/configxml.html#cvs)  It's 
> been around a long time and no one has complained about it yet.  Cvs

Actually CC has been an issue before, since in the past it has buried
servers with the load it puts on it.  I understood they'd fixed it... 
possibly not yet.

> files).  I need a single command that will tell me if the project has 
> changed since a specific time.  If cvs log is the wrong command, then 
> what is the right command?

There isn't one - you don't do it by polling, you do it by getting the
server to tell you when changes happen, or keep an updated sandbox and
check the last modification dates... polling the server is the wrong way
to do this.

> And is cvs log causing all the dead cvs.exe processes on my server?

If it's running cvs log on the entire repository then they aren't dead
they're probably still processing - it will take a long time to do that.

I'd terminate CC and see if the problem goes away.  The only other
possibility is Antivirus, and you've already said you don't want to
switch that of...

Tony