Re: Checking out without lock

[david]

> I have read access to the CVS repository but no write access.
> Obviously this means I cannot commit any changes.  But it ought to be
> possible to get a checkout.  However even if I turn off history
> logging, cvs co won't work because it wants to make a lock file.
> 
> Is there some option similar to -l to say do not make lock files when
> reading?  This means you could get an inconsistent checkout when
> someone updates the repository while you're reading, but that is a
> risk anyway for projects with more than one directory, and a risk I'm
> willing to take.
> 
Not that I know of.

The correct solution is for the administrator to set up separate
lock directories, with a line like
LockDir=/usr/cvs/cvslocks
in the CVSROOT/config file.

-- 
Now building a CVS reference site at http://www.thornleyware.com
address@hidden