[cvsnt] CHACL problem - why does CVS exist with code 0 when commit fails?

Karin Avramzon Karin at xmpie.com
Thu Apr 24 09:32:31 BST 2008

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.


I have set a "nowrite" permission to a file using CHACL.
I then tried to commit the changes in this file, via WinCvs client, and I expected the action to fail.
However, although the commit itself didn't take place, the WinCvs client returned the following:

cvs server: User AAA is unable to write to ./ReadMe.txt - ignoring
***** CVS exited normally with code 0 *****

Why does CVS exist with code 0 and not with code 1?
How will the user know that the commit actually didn't take place, if the returned error code is 0?

This is much more problematic when trying to commit files via Visual Studio, as then, since the returned error code is 0 - the action seem to have succeeded, although it didn't, and there's no visual indication to that.

A similar thing happens on 'Update', when there's "noread" permission on the file.
However, and 'Edit' action does provide code 1, when it fails on ACL.

Am I doing something wrong?
Please advise.


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook