Re: Stuck cvs lock on anoncvs repository

[Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>]

On Sun, Jun 28, 2009 at 4:17 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> the problem is that we transferred the locks from cvs.postgresql.org to
>> anoncvs.postgresql.org which confused cvs running on anoncvs.
>
> Ah, now I understand.  Yes, sounds like a simple --exclude will fix it.

From our experience, it's always better to put the locks outside of
the repository.

You should be able to set:
LockDir=/var/lock/cvs/your-repo
in the CVSROOT/config file.

(with /var/lock/cvs/your-repo a directory where every user accessing
the repository can write - readonly users included).

-- 
Guillaume