In a message dated 6/14/2000 10:27:10 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> [EMAIL PROTECTED] writes:
> >
> > I got everything working just nicely, but I ran into a bit of an
> > administration headache. I was hoping to be able to add users to
appropriate
> > groups in /etc/group so that a user could be part of more than one
group, but
> > it turns out the only way I can a user to have write-access to a
protected
> > module is if /etc/passwd lists the owning group as that user's primary
group.
>
> That *should* work -- how are you running CVS: local, rsh, pserver, etc.?
>
pserver running 1.10.8 on HP 10.20.
> > When I simply added "user2" to "group1" in /etc/group and did a commit,
I get
> > this error message:
> > cvs [server aborted]: could not open lock file
'/repos/cm/hal/,filename,':
> > Permission denied
> >
> > which is weird, since the LockDirs are in /lockdirs/cm/hal...
>
> The error message is somewhat misleading; that's actually the new RCS
> file -- once it's been successfully written, it gets renamed to the
> usual .../filename,v. (RCS uses the ,filename, file for locking, so
> it's an RCS lock file, not a CVS lock file.) Did you re-login after
> changing /etc/group? The `id' command should show you your current
> group membership, but it's set up at login time, it doesn't change
> dynamically with /etc/group.
>
But I don't want to have to change /etc/group for each access. I mean,
doesn't a user essentially "login" each time they run a CVS command with
pserver? So being a "member" of the group isn't enough, it has to be your
"primary" group?
Bummer. So LockDirs is really only useful for local repositories? Bummer
bummer.
I hate suggesting changes to CVS because I never know if I'm going to get
someone mad, but doesn't this kinda mean a "cvs newgrp" command would be
useful? (To go with the "cvs chmod" and "cvs chown" commands? ;) Maybe I
can get those nice folks at OpenAvenue to add them for $$$$ (which I have
more of than time).
Would that be a good idea or not?
:)hal mahaffey
