[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Checking out without lock

From: Ed Avis
Subject: Checking out without lock
Date: 04 Sep 2003 12:56:23 +0100

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.

% cvs -l -d :ext:somehost:/foo/cvs co myproject
cvs server: Updating myproject
cvs server: failed to create lock directory for
`/foo/cvs/myproject' (/foo/cvs/myproject/#cvs.lock):
Permission denied
cvs server: failed to obtain dir lock in repository
cvs [server aborted]: read lock failed - giving up

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.

Ed Avis <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]