File permission problem with cvs

[Patricia Liguori]

Hi.

We have been using cvs for several months now and all has been going
well.  Just recently we noticed that we are getting unexpected file
permissions.  For example, we have watches turned on so we would expect
that when we checkout files, they would be checked out as read-only. 
Well, that is not always the case.  There are some files that have
read-write permissions when checked out.  To confirm the problem, I
deleted my entire working directory and checked out a new copy of the
module.  When I did that, one file was read-write and the other were all
read-only.  Other developers on the project are also running into file
permission problems.  For example, one developer created a new file,
added the file and committed the file to cvs. (The log shows the file
and it's revisions.)  After committing the file, the file remains in
read-write state in his local directory.  There are also other problems
we are having along the same lines.  
Does any one have any ideas as to why this may be happening?  As far as
I know, the way that the developers have been using cvs hasn't changed,
although maybe it has and they are not aware that they are doing things
differently.  Any help would be greatly appreciated.

Thank you.

Patti

pshearn.vcf
Description: Card for Patricia Liguori