Yes, I have LockDir="/home/dotcvs/cvslocks" in config. The directory
does exist. I have played with /tmp/cvslocks and /var/tmp/cvslocks
and always get the 'cannot stat'. I have toyed will all sorts of
open permissions (e.g. chmod 777) on the locks dir and still does not
work. If I comment out LockDir, it all works fine. As mentioned in
first email, I want true read-only and writer access to repository.
LockDir is the first step right?
-wha
On Thu, 31 May 2001, Larry Jones wrote:
> William Asquith writes:
> >
> > I am trying to use LockDir with cvs1.10.7 on Linux. My root is
> > /home/dotcvs and I want locks in /home/cvslocks. I have played with
> > permissions but still get this:
> > cvs checkout: Updating junkcvs
> > cvs [checkout aborted]: cannot stat "/home/dotcvs/cvslocks": No
> > such file or directory
> > cvs [checkout aborted]: cannot stat "/home/dotcvs/cvslocks": No
> > such file or directory
>
> What does your CVSROOT/config file look like? It looks like you have
> LockDir=/home/dotcvs/cvslocks instead of LockDir=/home/cvslocks. And
> note that the LockDir must already exist -- CVS won't create it.
>
> -Larry Jones
>
> I won't eat any cereal that doesn't turn the milk purple. -- Calvin
>
William H. Asquith
Hydrologist
USGS, Austin, TX
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
