Stephen Vance wrote:
A simple approach is to set up two groups, P4Admin and dev, for
example. For the admin group, I deliberately chose something that is
*not*
either 'root' or 'Administrator' so that people logged in as one of these
on either Unix or Windows don't accidentally become these Perforce users.
Steve,
What are the advantages of having two groups? I would think
that
having groups would start paying off when three or more are required to
achieve additional granularity. For instance, we have several dozen users
all of whom
have read access to everything in every depot and each of whom has write
access to the depots of his or her application(s.) Then, we have the
'p4admin'
user and a handful of superusers with admin privileges. Why would we want
to implement Perforce groups? What am I missing?
Cheers,
Thom Wielski
Sybase Inc