Re: LockDir option in CVSROOT/config

[Larry Jones]

Peter Kroon writes:
> 
> 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.

As long as both systems are Unix-like, there's no problem: set LockDir
to some location *not* on the shared file system, and then create
symlinks on each system at that location pointing to the correct
directory in the shared filesystem.

> 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 ....?

When LockDir is not specified, the lock files go in $CVSROOT.  LockDir
is intended to be specified as an absolute path; while there's nothing
to prevent you from specifying a relative path, CVS changes directory
while it's working, so I doubt that it would work correctly.

-Larry Jones

I'm a genius. -- Calvin