Behaviour of writing to history file

[Paul Ackersviller]

We have just upgraded to 1.11.23 from at least a few patchlevels earlier,
and have noticed started receiving lock errors (on CVSROOT/.#cvs.history...
or something close to that) for users not in the administrative group.
We keep our CVSROOT/ group-protected, and it looks to me like the method
of writing to the history files has changed.

Is there any way to keep the same admin-file protection without disabling
history or opening up permissions, and without running too ancient of a
version?

[Larry Jones]

Post by Paul Ackersviller
We have just upgraded to 1.11.23 from at least a few patchlevels earlier,
and have noticed started receiving lock errors (on
CVSROOT/.#cvs.history...
or something close to that) for users not in the administrative group.
We keep our CVSROOT/ group-protected, and it looks to me like the method
of writing to the history files has changed.

Yes, locking was added to prevent the history file from getting corrupted by
multiple people trying to write to it at the same time.

Post by Paul Ackersviller
Is there any way to keep the same admin-file protection without disabling
history or opening up permissions, and without running too ancient of a
version?

Use the LockDir= option in CVS/config to move the lock files out of the
repository.

http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_18.html#SEC195

-Larry Jones