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.
Hi, After using cvsnt for many, many months, I finally managed to crash the cvsnt server; I got the cute 'Something bad happened to CVSNT' message :). It also locked my Win 2003 sever quite amazingly... it appeared that the CPU was looping somewhere in cvsnt and not enough cycles were available for me to login as admin and reset the system properly... I had to resort to the BIG RED SWITCH (well, actually the small silver coloured push button, but I still fondly remember the days when it would have been a Big Red Switch). I'm running 2.0.41a at both client and server ends. What I was doing was, IMHO, quite innocent ;-) I've got two snapshots of a web site that I'm bringing into cvsnt. So, I thought I'd use the import feature, and in particular, make use of the -n feature (which is where I think the problem could be). This is what I was doing: in a directory containing the first snapshot: cvs import -d -ko -I! -m "snapshot" -n www followed by cvs rtag D_2001-07-25 www All works well. Then, moving into the second directory containing the second snapshot: cvs -t import -d -ko -I! -m "snapshot" -n www And this is where things go wrong. It appears to process all the files, but on the last file the client just sits there. This is what I get: cvs server: Importing D:/CVS/REPO/trevezel/www/downloads N www/downloads/draft-somers-ftp-mfxx-00.html S -> set_repository_version((null),(null)) N www/downloads/draft-somers-ftp-mfxx-00.txt S -> set_repository_version((null),(null)) ctrl-c stops it (although at this stage the cvsnt server it is a bit of a wobbly state, and the best thing to do is stop then restart it... otherwise 'Something bad happened to CVSNT' will happen). The funny thing is that after restarting the cvsnt service, the second import seems to have worked fine... all the files are there. Has anybody else had any problems like this? I assume its because I'm using the -n option with import... if I use import without -n and specify vendor and release tags all works well. Greetings from Luxembourg, David