| From: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-www(at)postgresql(dot)org |
| Subject: | Re: Stuck cvs lock on anoncvs repository |
| Date: | 2009-06-29 21:12:02 |
| Message-ID: | 1d4e0c10906291412o44033e25j6cc370f70d4e89d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Filip Rembiałkowski | 2009-06-29 21:21:19 | dead link in search results hint |
| Previous Message | Dave Page | 2009-06-29 18:44:34 | Re: PostgreSQL moderation report: 2009-6-29 |