[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.?
> 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.
-Larry Jones
TIME?! I just finished the first problem! -- Calvin
