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 firstname.lastname@example.org.
Thanks chuck for the reply, > What you'll probably find is that your history file has some minor > corruption. Can you explain what kind of corruptions may have my history file? Is it easy to fix? And how those corruptions may happen? > Older versions of cvs would ignore these lines, the latest versions of > cvsNT treat it as an error and return -1. > We run a cron job hourly to clean up the history file. I can give you my > python script if you like. Yes. Please. > The solution that was recommended to me was to turn off the history file > and turn on auditing. >That requires a database, and of course the history command no longer > works. Instead you need to do sql queries against the database. This > approach may suit you better. It wasn't the right solution for us. I wouldn't turn off history file. My aim is precisely to make it work with a build automation tool (luntbuild) in order to improve performance. Thanks again, NG.