permissions question
Hello all: I am managing an unusual situation where we need to have several developers working on the same directory tree. Essentially I am using CVS as a logging mechanism, and to track revisions, but the software in question will only work in one place (don't ask). The problem is that each time I check something in, CVS changes the file's permissions to 755, so that my teammates can't change it. How do you control this behavior? I believe this behavior is also responsible for occasional "up-to-date check failed" messages. Since there is only one developer tree, there are no other versions of these files to change. These messages, I assume, are also caused by an owner or permission mismatch. Any advice? Many thanks, -tom tomfool at as220 dot org http://sgouros.com http://whatcheer.net ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: permissions question
[EMAIL PROTECTED] wrote: > The problem is that each time I check something in, CVS changes the file's permissions to 755, so that my teammates can't change it. How do you control this behavior? use directories setgid bit to ensure files checked in will stay group-writable. -- All warranty and guarantee clauses become void upon payment of the final invoice -- Financial General Shefields Corollaries n°2 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: permissions question
chmod 2775 dirname <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Hello all: > > I am managing an unusual situation where we need to have several > developers working on the same directory tree. Essentially I am using > CVS as a logging mechanism, and to track revisions, but the software > in question will only work in one place (don't ask). > > The problem is that each time I check something in, CVS changes the > file's permissions to 755, so that my teammates can't change it. > How do you control this behavior? > > I believe this behavior is also responsible for occasional "up-to-date > check failed" messages. Since there is only one developer tree, there > are no other versions of these files to change. These messages, I > assume, are also caused by an owner or permission mismatch. > > Any advice? > > Many thanks, > > -tom > > > tomfool at as220 dot org > http://sgouros.com > http://whatcheer.net > > ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
can't commit! permissions question
Who is supposed to be the owner of the files that are in the respository? I can update and checkout but not commit. Obviously the permissions are wrong somewhere. I've been looking in the OpenSourceDevelopment with CVS by Fogel and in the Cederqvist but I must conclude I've just not run across the needed info or it's not there. The accounts on the unix box are cvsadmin,sc, and jschwenk. The files in the repository are owned by sc but I'm logged in as cvsadmin. I imported a new directory of files as user jschwenk. I just checked in the repository and those files are owned by jschwenk. Does that mean that no one but jschwenk can commit these files? How do other individuals ever checkout/commit then? How can permissions be controlled? Does one need to give files a different user before checking in? Here's the passwd file. anonymous:!: cvsadmin:6Ji: dkennedy:Jul:sc pkuah:Jul:sc jschwenk:Jul:cvsadmin As cvsadmin, I can't commit the changes that were sent to me from the contractors because I don't have proper permissions. If any of this is unclear, please email me directly cause I need help! Jeanie ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: can't commit! permissions question
Schwenk, Jeanie writes: > > Who is supposed to be the owner of the files that are in the respository? I > can update and checkout but not commit. Exactly what error messageare you getting? In general, you need read access to the files and write access to the directory. Files are owned by the last user to update them, directories are owned by the user who added them. If you're on a SysV-like system (most notably Linux), you may find it useful to set the SGID bit on all the repository directories (chmod g+s) -- that will cause newly-created directories to inherit their groupid from the parent directory instead of using the groupid of the creator. -Larry Jones Hmm... That might not be politic. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: can't commit! permissions question
I've included two examples below complete with error messages. The first is me logged into cvs as user cvsadmin in the cvsgrp group. There are two modules: rat and DEV. The second example is me logged in as user jschwenk in the users group. Unfortunately, I did not set up the initial repository nor did I install cvs. Are the files supposed to be read-only? Example 1: Here's the top level directory of the DEV module drwxrwxr-x 6 sc users 1024 May 25 13:53 environments drwxrwxr-x 11 sc users 1024 May 25 13:57 source all the files are read-only (just listed a few) -r--r--r-- 1 sc users19489 May 25 12:53 IDTGUI_Bundle_de_DE.properties,v -r--r--r-- 1 sc users18044 May 25 12:53 IDTGUI_Bundle_en_US.properties,v -r--r--r-- 1 sc users 1201 May 25 12:53 IDTGUI_CustomisedBundle_de_DE.properties,v Error while accessing C:\Macros (error 2) CVSROOT: :pserver:cvsadmin@pilot:/export/cvsroot (password authentication) TCL is available, shell is enabled : help (select and press enter) cvs -z9 login (Logging in to cvsadmin@pilot) *CVS exited normally with code 0* cvs -z9 checkout -P rat (in directory C:\) cvs checkout: in directory rat: cvs checkout: cannot open CVS/Entries for reading: No such file or directory cvs server: Updating rat U rat/RatComm.java cvs checkout: cannot open CVS/Entries.Log: No such file or directory U rat/RatGuiPilot.java cvs checkout: cannot open CVS/Entries.Log: No such file or directory cvs server: Updating rat/scripts cvs server: failed to create lock directory for `/export/cvsroot/rat/scripts' (/export/cvsroot/rat/scripts/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/export/cvsroot/rat/scripts' cvs [server aborted]: read lock failed - giving up *CVS exited normally with code 1* cvs -z9 checkout -P DEV (in directory C:\) cvs checkout: in directory dev: cvs checkout: cannot open CVS/Entries for reading: No such file or directory cvs server: Updating dev cvs server: failed to create lock directory for `/export/cvsroot/systema/environments/dev' (/export/cvsroot/systema/environments/dev/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/export/cvsroot/systema/environments/dev' cvs [server aborted]: read lock failed - giving up *CVS exited normally with code 1* Example 2: cvs -z9 checkout -P DEV (in directory C:\) cvs server: Updating dev cvs server: failed to create lock directory for `/export/cvsroot/systema/environments/dev' (/export/cvsroot/systema/environments/dev/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/export/cvsroot/systema/environments/dev' cvs [server aborted]: read lock failed - giving up *CVS exited normally with code 1* -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 07, 2001 11:56 AM To: Schwenk, Jeanie Cc: [EMAIL PROTECTED] Subject: Re: can't commit! permissions question Schwenk, Jeanie writes: > > Who is supposed to be the owner of the files that are in the respository? I > can update and checkout but not commit. Exactly what error messageare you getting? In general, you need read access to the files and write access to the directory. Files are owned by the last user to update them, directories are owned by the user who added them. If you're on a SysV-like system (most notably Linux), you may find it useful to set the SGID bit on all the repository directories (chmod g+s) -- that will cause newly-created directories to inherit their groupid from the parent directory instead of using the groupid of the creator. -Larry Jones Hmm... That might not be politic. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: can't commit! permissions question
"Schwenk, Jeanie" wrote:
> I've included two examples below complete with error messages. The first is
> me logged into cvs as user cvsadmin in the cvsgrp group. There are two
> modules: rat and DEV. The second example is me logged in as user jschwenk
> in the users group. Unfortunately, I did not set up the initial repository
> nor did I install cvs. Are the files supposed to be read-only?
Yes. You need write permissions in the directory or in the LockDir (read about
the 'config' file in the CVS manual) even to check out files.
It's possible that the user you have CVS running as isn't a member of the
'user' group it appears you $CVSROOT is owned by. Either change the
owner/group of the files and directories under $CVSROOT or change the
user/group that the cvs server runs as. As Larry mentioned, sometimes setting
the setgid bit ('man chmod') helps too.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net )
--
If nature has made any one thing less susceptible than all others of exclusive
property, it is the action of the thinking power called an idea, which an
individual may exclusively possess as long as he keeps it to himself; but the
moment it is divulged, it forces itself into the possession of everyone, and
the receiver cannot dispossess himself of it. Its peculiar character, too, is
that no one possesses the less, because every other possesses the whole of it.
He who receives an idea from me, receives instruction himself without lessening
mine; as he who lights his taper at mine, receives light without darkening me.
That ideas should freely spread from one to another over the globe, for the
moral and mutual instruction of man, and improvement of his condition, seems to
have been peculiarly and benevolently designed by nature, when she made them,
like fire, expansible over all space, without lessening their density at any
point, and like the air in which we breathe, move, and have our physical being,
incapable of confinement or exclusive appropriation. Inventions then cannot, in
nature, be a subject of property.
- Thomas Jefferson
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: can't commit! permissions question
Schwenk, Jeanie writes: > > Unfortunately, I did not set up the initial repository > nor did I install cvs. Are the files supposed to be read-only? Yes. > cvs -z9 checkout -P rat (in directory C:\) > cvs checkout: in directory rat: > cvs checkout: cannot open CVS/Entries for reading: No such file or directory That looks like the directory you're trying to checkout into (rat) already exists -- CVS really wants to create it. > cvs server: failed to create lock directory for > `/export/cvsroot/rat/scripts' (/export/cvsroot/rat/scripts/#cvs.lock): > Permission denied That means that you don't have write permission in the /export/cvsroot/rat/scripts directory. > cvs -z9 checkout -P DEV (in directory C:\) > cvs checkout: in directory dev: > cvs checkout: cannot open CVS/Entries for reading: No such file or directory Same as above. > cvs server: failed to create lock directory for > `/export/cvsroot/systema/environments/dev' > (/export/cvsroot/systema/environments/dev/#cvs.lock): Permission denied Ditto. > cvs server: failed to create lock directory for > `/export/cvsroot/systema/environments/dev' > (/export/cvsroot/systema/environments/dev/#cvs.lock): Permission denied Ditto. -Larry Jones I'm getting disillusioned with these New Years. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
