Re: RCS lock files

[Derek R. Price]

Larry Jones wrote:

> Derek R. Price writes:
> >
> > Creating the RCS lock/temp files in the repository regardless of the
> > LockDir setting makes it impossible to give a specific user write access
> > only to specific files in a directory (i.e. the user has read access to
> > the directory but write access to specific files).  This could be seen
> > as, at least, lack of a useful feature in the case of $CVSROOT/CVSROOT.
>
> It's the only way I know to ensure that an unfortuately timed system
> crash doesn't leave you with a missing or corrupt RCS file (rename n
> within a directory is an atomic operation on most modern systems).

Hmmm.   A daemon which copies the temp file into the appropriate directory
before the rename is more than I want to get into right now.  Maybe when the
CVS server becomes reentrant.  Hah.

Are there any systems which will guarantee an atomic operation if the rename
doesn't change the partition the file resides on?  Enough to justify a
LockDirMode option or the like?  Or maybe this is something that could be
tested for with configure?  I'm not sure how I'd go about that and I didn't
find anything in a quick search of the Autoconf docs, but you never know.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:dprice@openavenue.com     OpenAvenue ( http://OpenAvenue.com )
--
I will not skateboard in the halls.
I will not skateboard in the halls.
I will not skateboard in the halls...

          - Bart Simpson on chalkboard, _The Simpsons_