info-cvs
[Top][All Lists]
Advanced

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

gid setting and permissions


From: Mick
Subject: gid setting and permissions
Date: Thu, 1 Nov 2001 17:23:59 -0800 (PST)

Hi, again this might be a dumb question, but bear with
me for a second :-)

I am in the process of setting up cvs at work.

We have two users, let's say they are named user1 and
user2.  Their gid is 'user1' and 'user2' respectively.
 They also both belong to 'cvs' gid. 

When user1 imports a module into the repository, it
seems that it is stored with user1:user1 ownership in
the repository.  Now the problem is that when user2
wants to checkout that module, he/she gets the
following error.

address@hidden user2]$ cvs checkout test2
cvs checkout: Updating test2
cvs checkout: failed to create lock directory for
`/home/cvsroot/test2' (/home/cvsroot/test2/#cvs.lock):
Permission denied
cvs checkout: failed to obtain dir lock in repository
`/home/cvsroot/test2'
cvs [checkout aborted]: read lock failed - giving up

Is this an expected behaviour?  Or am I doing
something wrong?  I came up with two different ways of
looking at this.

1. Obviously user1 can have his own modules which he
doesn't want others to see, so this is the correct
behaviour.
2. No matter who imports a module, it should be
available to all developers.

Which one is correct?

Thanks in advance.

__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com



reply via email to

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