Re: LockDir option in CVSROOT/config

[Peter Kroon]

"Reinstein, Shlomo" <address@hidden> wrote in message
news:address@hidden
> Hi,
>
> We're using CVS on both Windows and Linux, using the ":local:" access
> method. Our repository is located on AFS, from Linux it's accessible
as
> "/afs/...", and from Windows the repository is accessible using some
drive
> letter that is mapped to the root of AFS.
> I now want to use the LockDir option in CVSROOT/config to change the
> location where CVS creates its lock directories, but I have a problem:
How
> do I specify a directory in a way that will be meaningful to CVS on
both
> Windows and Linux? If I use "/afs/...", CVS on Windows won't accept
that,
> and if I use ":local:z:\...", CVS on Linux won't accept that.
> I know that the natural solution is a CVS server - but it's not
trivial for
> us to switch to client/server because of some administrative issues,
and it
> will take time until we get there. For the mean time - how do I make
LockDir
> work? I noticed that I cannot specify relative locations (e.g.,
../Locks).
> Is there an option to specify the directory relative to the CVSROOT?
>
> Shlomo
>

We've run into a similar problem and have the same questions.
 The repository is on an NFS server.
Two Linux systems need access to this repository.

System A is our CVS server and accesses the repository as an NFS mounted
directory /home/...

System B is our web server which runs the cgiweb.cgi script (by Bill
Fenner,
Henner Zeller, Henrik Nordstr?m, Ken Coar) which requires local CVS.
This
system already has its own local /home and has to mount the NFS
directory
as something other than /home. We use /rhome.

As the cvsweb.cgi script needs local CVS the server solution doesn't
work
here.

As cgsweb.cgi requires write access for creating the lock files, and we
don't
want to give the web server write access to the repo, we though that
using LockDir in CVSROOT/config would be a good option. But with the
problem Shlomo describes this seems to be impossible.

We were also wondering where exactly the lock files go when no LockDir
is specified. And whether LockDir specifies an absolute path or
something
relative to the root of the repository, or ....?

Peter Kroon.