Great, thanks.
Original Message Follows
From: Jim Hyslop <[EMAIL PROTECTED]>
To: S I <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], info-cvs@gnu.org
Subject: Re: Repository Access
Date: Thu, 16 Jun 2005 14:50:05 -0400
MIME-Version: 1.0
Received: from tomts22-srv.be
S I wrote:
cvs_acls? Ok thanks. I have to research that. Is that a 3rd party tool
or part of CVS?
It's part of the source code distributed from www.cvshome.org. Download
the tarball (or check out the source) and cvs_acls will be in a
directory named 'contrib'.
cvs_acls provides more fine-
cvs_acls? Ok thanks. I have to research that. Is that a 3rd party tool or
part of CVS?
Original Message Follows
From: Todd Denniston <[EMAIL PROTECTED]>
To: S I <[EMAIL PROTECTED]>
CC: info-cvs@gnu.org
Subject: Re: Repository Access
Date: Thu, 16 Jun 2005 08:56:09 -0500
PROTECTED] proj-C only
So, looks like I have to create different unix groups, etc. Thanks for the
response.
Steve
Original Message Follows
From: Jim Hyslop <[EMAIL PROTECTED]>
To: S I <[EMAIL PROTECTED]>
CC: info-cvs@gnu.org
Subject: Re: Repository Access
Date: Thu, 16 Ju
Jim Hyslop wrote:
>
> S I wrote:
> > Hi Class!
> >
> > Currently our CVS repo has 3 main & separate projects running under it.
> > By default when I create a new unix user; I give them access to the
> > whole repository, however, some folks have been editing files in
> > projects they were not sup
S I wrote:
Hi Class!
Currently our CVS repo has 3 main & separate projects running under it.
By default when I create a new unix user; I give them access to the
whole repository, however, some folks have been editing files in
projects they were not supposed to.
How can I ONLY and specifica
Thanks a million...I'm must be getting pretty good at this :-)
It actually worked, with permissions and everything!
Olav!
Larry Jones wrote:
> Olav =?ISO-8859-1?Q?Lindkj=F8len?= writes:
>
>>cvs server: cannot open /root/.cvsignore: Permission denied
>>cvs [server aborted]: can't chdir(/root):
Olav =?ISO-8859-1?Q?Lindkj=F8len?= writes:
>
> cvs server: cannot open /root/.cvsignore: Permission denied
> cvs [server aborted]: can't chdir(/root): Permission denied
That means you're missing the -f in server_args or you need to add
"passenv = PATH" to your xinetd configuration file.
-Larry
>>but when I try to checkout a module it says: "setgid failed: operation
>>not permitted". I have the modules owned by their respective user:group
>>and have done a "chmod 2770 ". What have I missed?
>>
>
> That indicates that you're not running CVS as root (from [x]inetd). If
> you want CVS t
Olav =?ISO-8859-1?Q?Lindkj=F8len?= writes:
>
> but when I try to checkout a module it says: "setgid failed: operation
> not permitted". I have the modules owned by their respective user:group
> and have done a "chmod 2770 ". What have I missed?
That indicates that you're not running CVS as roo
I cant get access to the repository after following your suggestions. I
think I got it the way you described it. I can login to the server ok,
but when I try to checkout a module it says: "setgid failed: operation
not permitted". I have the modules owned by their respective user:group
and have
Thanks alot for all the help...I'll try and get it done during the weekend.
I'll let you know if it works or not.
Regards from Olav!
Rob Helmer wrote:
> On Thu, Jan 24, 2002 at 06:01:31PM -0500, Douglas Finkle wrote:
>
>>>:-) I have SSH, CygWin, and Putty on my windoze box. Tortoise
>>>CVS co
On Thu, Jan 24, 2002 at 06:01:31PM -0500, Douglas Finkle wrote:
> > :-) I have SSH, CygWin, and Putty on my windoze box. Tortoise
> > CVS comes with SSH via a DOS window...and you have to punch in the
> password for
> > every CVS command. Thats not very user friendly for people
> > totally blan
>> > Disclaimer: I think this is all...
Oh yeah, admin user cvs should be in all groups... cvs, public, company[abc]
> =
> Thanks for the detailed answer!
ur welcome.
> Now for the trick question: If I am not going to use pserver, what is
> the easiest to set up, a
> Close, but I do not completely agree:
>
> - Admin group cvs-- nobody else, create an unpriviledged admin role user cvs
> - Set (almost, see next line) all files under $CVSROOT/CVSROOT to cvs:cvs
> - set $CVSROOT to cvs:public 0750, $CVSROOT/history, val-tags to 0660
> cvs:public
> - Each compa
On Thu, Jan 24, 2002 at 04:26:45PM -0500, Douglas Finkle wrote:
> Close, but I do not completely agree:
You're right! I misread the requirements. Sorry.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
One ring to rule the mall.
- Movie review headl
> On Thu, Jan 24, 2002 at 05:44:51PM +0100, Olav Lindkjølen wrote:
> > In short:
> > ---(Admin) must have read/write access to all modules.
> > ---Users from Company B must have read/write access only to
> modules with
> > code owned by them.
> > ---Users from Company B must allso have Read Only
On Thu, Jan 24, 2002 at 05:44:51PM +0100, Olav Lindkjølen wrote:
> In short:
> ---(Admin) must have read/write access to all modules.
> ---Users from Company B must have read/write access only to modules with
> code owned by them.
> ---Users from Company B must allso have Read Only Access to publ
18 matches
Mail list logo
