Re: File checks out as writeable

[Colin Brough]

> On occasion, I've run across files that check out as writeable (766
> perms) for no apparent reason when performing a 'co -r2 $file'.  Other
> files in the same source directory check out with a normal 666 perms.
> The only way that I've found to correct this problem was to remove the
> ,v file entirely from the archive, and then check it back in.  Of
> course, to maintain build reproducibility/history, I need to recreate
> all revisions and apply the appropriate labels.
> It seems that there must be a better solution.  

>From 'man co':

FILE MODES
       The working file inherits the read and execute permissions from the RCS
       file.  In addition, the owner write permission is turned on, unless -kv
       is set or the file is checked out unlocked and locking is set to strict
       (see rcs(1)).

and from 'man rcs':

       -L     Set locking to strict.  Strict locking means that the  owner  of
              an RCS file is not exempt from locking for checkin.  This option
              should be used for files that are shared.

       -U     Set locking to non-strict.  Non-strict locking  means  that  the
              owner  of  a  file  need  not lock a revision for checkin.  This
              option should not be used for files that  are  shared.   Whether
              default  locking is strict is determined by your system adminis-
              trator, but it is normally strict.

My guess is that the problem files have, somehow, had their locking
set to non-strict.

Cheers

Colin

----------------------------------------------------------------------
Colin Brough                             address@hidden