[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: failed to create lock directory
From: |
Larry Jones |
Subject: |
Re: failed to create lock directory |
Date: |
Tue, 5 Feb 2002 15:03:11 -0500 (EST) |
Steve Ebersole writes:
>
> However, now when I try to perform a checkout as this "anonymous" user, cvs
> is unable to lock CERTAIN directories. For example, It was able to check
> out code from a directory .../models, but not from .../models/handlers even
> though ownership and permissions are exactly the same on both directories.
>
> I searched the mailing list archives for this issue, but most assumed this
> was a file-system level write-permission issue. I don't see how this can be
> a problem with the file system permissions iin this scenario (the repository
> "/u02/cvs" and all of its subdirectories are owned by the user cvsadmin who
> is a member of the same cvsadmin group to which the cvsanon user belongs.
The most likely scenario is that you have LockDir= in your
CVSROOT/config file so the locks are going into a different
directory tree where the permissions are *not* the same.
-Larry Jones
I hate it when they look at me that way. -- Calvin