Jeff Frost wrote:
> damien clochard wrote:
>> Jeff Frost a écrit :
>>   
>>> damien clochard wrote:
>>>     
>>>> Hi !
>>>>
>>>> As i said 6 months ago, it is impossible to checkout the slony's website
>>>> CVS :
>>>>
>>>> $ export CVSROOT=":pserver:anonymous at main.slony.info:/slony1"
>>>> $ cvs co slony1-www/
>>>> cvs checkout: Updating slony1-www
>>>> cvs checkout: failed to create lock directory for `/slony1/slony1-www'
>>>> (/slony1/slony1-www/#cvs.lock): Permission denied
>>>> cvs checkout: failed to obtain dir lock in repository `/slony1/slony1-www'
>>>> cvs [checkout aborted]: read lock failed - giving up
>>>>
>>>>
>>>> Am i doing something wrong ? Is there a reason for not giving public
>>>> access to this repository ? Maybe the CVS is not used anymore ? If this
>>>> is a problem, what can i do to help ?
>>>>   
>>>>       
>>> Looks like you forgot to "cvs login".  Just do it like so:
>>>
>>> CVSROOT=":pserver:anonymous at main.slony.info:/slony1" cvs login
>>> CVSROOT=":pserver:anonymous at main.slony.info:/slony1" cvs co slony1-engine
>>>
>>>     
>>
>> I did the cvs login and pressed [Enter] when i was prompted for password.
>>
>> It works fine for the slony1-engine repository but it fails for the
>> slony1-www repository.
>>
>>   
> Ah!  I'm sorry, I misread your original post that indicated 
> slony1-www. :-(  The slony1-www fails for me in the same way.  I'm 
> going to guess that the anonymous user doesn't have write access to 
> that directory and not too many people check out the slony1-www repo 
> as anonymous so it hasn't been noticed until now.  Hopefully one of 
> the admins can fix that.
> cbbrowne at main:/home/cvsd$ ls -l /home/cvsd/fixperms.sh
> -rwsr-sr-x 1 root root 131 Apr 24  2007 /home/cvsd/fixperms.sh
> cbbrowne at main:/home/cvsd$ cat /home/cvsd/fixperms.sh
> #!/bin/sh
> chown -R cvsd /home/cvsd/slony1/slony1-engine
> chmod -R og+s /home/cvsd/slony1/slony1-engine /home/cvsd/slony1/slony1-www
>
I'm not quite sure what's wrong here...

There are a few places that document a common group permissions issue 
that looks as though it might cause this; characteristic is...  
http://www.mooreds.com/wordpress/archives/000234

In poking around, the permissions *appear* appropriate in /home/cvsd and 
children.

There's a script there that looks like it might rectify things; I don't 
have permission to run it...  Devrim?

cbbrowne at main:/home/cvsd$ ls -l /home/cvsd/fixperms.sh
-rwsr-sr-x 1 root root 131 Apr 24  2007 /home/cvsd/fixperms.sh
cbbrowne at main:/home/cvsd$ cat /home/cvsd/fixperms.sh
#!/bin/sh
chown -R cvsd /home/cvsd/slony1/slony1-engine
chmod -R og+s /home/cvsd/slony1/slony1-engine /home/cvsd/slony1/slony1-www