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.
David, Also the info I asked for earlier (from process explorer) would also help pinpoint what these processes are/were doing and may help identify what "client" is responsible for them... If you have VS.NET 2003 on the server we could even pinpoint the line of code they are stopped at... As a CC replacement we offer our own Build integration in CVS Suite, it doesn't do e-mails - but the standard CVSNT e-mail plugin can do that. Bascially the Make plugin only gets fired after a commit and passes info such as the module committed and the branch in easy to use parameters so that you can conect it easily to your build system. Regards, Arthur Barrett -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Tony Hoyle Sent: Thursday, 26 January 2006 11:02 AM To: cvsnt at cvsnt.org Subject: Re: [cvsnt] Dead cvs.exe processes David Jackman wrote: > I shut down CC again and killed all cvs.exe processes on the CC > machine (there were 5, and only one was doing a log command--the > others were executing update and checkout commands). After doing this > (and waiting a few minutes), there were still 349 cvs processes > running on the CVS server. > Then something is holding the processes open... Normally that's AV/Firewall issues. Run cvsdiag on the server & post the output. Tony _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook