Re: *some* files get checked out readonly

[Dale Miller]

John,

Check your umask.
If your umask is 022 your files will be 644.
If your umask is 02 your files will be 664.
If your umask is 0 your files will be 666.

Below is a test I did on a DEC alpha
     (uname -a = OSF1 cmp V4.0 878 alpha)
With version 1.11 of CVS using pserver mode.
Concurrent Versions System (CVS) 1.11 (client/server)


testit: rm -rf cm_tools/change
testit: umask 022
testit: cvs co cm_tools/change
U cm_tools/change
testit: ls -l cm_tools/change
-rwxr-xr-x   1 miller   miller    104360 Mar 15 00:37 cm_tools/change

testit: rm -rf cm_tools/change
testit: umask 02
testit: cvs co cm_tools/change
U cm_tools/change
testit: ls -l cm_tools/change
-rwxrwxr-x   1 miller   miller    104360 Mar 15 00:37 cm_tools/change

testit: rm -rf cm_tools/change
testit: umask 0
testit: cvs co cm_tools/change
U cm_tools/change
testit: ls -l cm_tools/change
-rwxrwxrwx   1 miller   miller    104360 Mar 15 00:37 cm_tools/change

Dale Miller


John Klassa wrote:

> I've looked through the FAQ, but don't see an answer to this question.
>
> I've got a whole subdirectory (for example) in which some of the files
> *always* get checked out and updated read-only, while others don't.  I
> don't have any special CVS variables (like CVS_READ, or whatever it is)
> set.  In the repository, all of the permissions on the files are the
> same (444).  There does not appear to be anywhere that permissions bits
> are being cached, yet some of the files are always 664 upon checkout
> (and after a checkin), and others (the same others) are 444.
>
> I'm using a pserver setup.
>
> Any ideas?  This is driving me nuts. :-)
>
> Thanks,
> John
>
> --
> John Klassa / address@hidden
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs