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 Tony, Thanks for the help on this problem. I think I finally figured out my problem. I thought I would reply back to the group to provide feedback in case anyone else runs into the same problem I had. I determined the problem was an incompatibility between CVSNT, the Gigabit Ethernet card, and using compression. It turns out that when I issued the command "cvs -z3 history -e" the server would crash. If I left off -z3 or -e the server didn't crash. I think there is an incompatibility of the compression and the Gigabit Ethernet card. I think the -e part was needed to make the command run long enough on the server to bring out the problem. (Also need to have a history file in CVSROOT that's at least 300K in size.) When I switched to a different Ethernet card, a 10/100 built into the mother board running at 100 Mbits full duplex, the problem went away. (I went from crashing the server every time I ran the command dozens of tries with no problem.) It might be helpful if someone who has there server on Gig-E with a history file of 300K or more could run the command "cvs -z3 history -e" and see if there's crash. Thanks, Curtis Lehman -----Original Message----- From: Tony Hoyle [mailto:tmh at nodomain.org] Sent: Wednesday, September 29, 2004 5:21 PM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: cvs -z3 history -e crashes server instantly. Lehman, Curtis wrote: > Ops. Wrong subject line and One correction bellow. A value of 0 or no -z > command Does Not crash it. Values of 1,3, and 9 DO crash the box. > As CVSNT is a userspace program it can't by itself cause a bluescreen... bluescreens are driver exceptions. The worst I've seen was when the LSA helper was stablilising and it could cause the LSA to shut down - it wouldn't have bluescreeened even then (that particular problem doesn't affect 2.0.51). Try running memtest86 on the box to make sure your memory is OK. Also stress the various parts of the system eg. the network to make sure there are no issues there. Tony _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs