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, i'm testing these days a new cvs server for production use. I'm using the latest 2.5.0.3 server installed on a highly customized Slackware 10.2 . The only quirk found is an unexpected behavior while tagging an entire repository: unexpected by my users at least. The actual production server cvsnt version used is a 2.0.0 beta 3 (don't comment please......) on a windows 2000 server service pack 3 (don't comment again, please....). On this version when a user (usually compilation managers) does a tag on an entire module others cannot commit or edit a single file in the entire module. Fortunately, by my point of view, new cvsnt has a more intelligent file locking mechanism. When the same user does a tag on the entire module, others are not locked and can do operations on files, but if someone happens to do that operation at the same time as the compilation manager tag, cvsnt starts to decide which process has precedence and after some try kills one while letting the other finish the operation. Both users are notified via log, but this behavior could cause potential troubles. I know that on a 20000 files tag the probability that this operations gets interrupted by a single file operation is less than likely, but since it has to be considered in a critical production environment, i would like to be informed better on the matter in order to have an ampler perspective on the matter and eventually find some solution. This kind of tagging happens every day in order to build the latest build number of the software. Compiling errors due too cvsnt erroneous tagging are quite undesirable ;-) I don't have the logs here at the moment, but feel free to ask in case they're needed. Alberto