[cvsnt] Dead cvs.exe processes

[David Jackman]

The CVS server is running Symantec AV, and I can't remove it (our
company IT policies forces this).  I am also running CruiseControl on
our build machine.  I thought it was configured correctly--what should I
look out for?

..David..


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Tony Hoyle
Sent: Monday, January 23, 2006 4:06 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Dead cvs.exe processes

Bo Berglund wrote:

> Possibly AntiVirus software? I don't have any AV on my CVS servers 
> because they are not used on the console and the absence of AV lessens

> the chance of file system interference with CVSNT.
> 
In the past AV has been known to hold the connections open, so the
process can't finish.. not heard of that for a while though (forget
which AV did that one).

Of course realtime scanning on the server will make the processes take
nearly forever...  That must be disabled or performance will totally
suck.

Another biggie is things like Cruise Control, which if misconfigured
starts multiple simultaneous checkouts, eats all the memory, so the
server eventually grinds to a halt.

Once a server reaches overload it just progressively dies - that happens
usually just after it starts going heavily into swap (true of all apps,
but cvsnt is a big memory user so you have to be careful with it).

(The rule of thumb still holds... about 12-15mb/simultaneous user, and
about enough disk space to hold a checked out sandbox * number of
users).

Tony
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt