[p4] Getting creative with the protection table

[NIGGEMYER Brant]

Yes, that would be excellent.

-----Original Message-----
From: Weintraub, David [mailto:david.weintraub at bofasecurities.com] 
Sent: Friday, May 12, 2006 2:29 PM
To: NIGGEMYER Brant; Arnt Gulbrandsen; perforce-user at perforce.com
Subject: RE: [p4] Getting creative with the protection table

Actually, it would be nice if Perforce allows you to specify the
protection on individual commands instead of just the six groups (list,
read, open, write, admin, super). That way, I could prohibit users from
running the jobspec or obliterate commands even if they are admin users.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of NIGGEMYER Brant
Sent: Friday, May 12, 2006 9:56 AM
To: Arnt Gulbrandsen; perforce-user at perforce.com
Subject: Re: [p4] Getting creative with the protection table

We've asked perforce to take away obliterate permissions from Admins and
only allow superusers to do oblits.  In our case, it is because we want
certain people to be able to add and remove users, but not have them do
oblits.

This is in the same vein as your request, so call or email perforce and
add yourself to the list of people wanting that feature.
 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Arnt
Gulbrandsen
Sent: Friday, May 12, 2006 8:53 AM
To: perforce-user at perforce.com
Subject: Re: [p4] Getting creative with the protection table

Ouch.

William Ivey writes:
> Oddly enough, if they do run obliterate it looks like it succeeded, 
> but it doesn't. At least not with a 2005.1 server (if you have a 
> different version it's worth testing to make sure). Editing changelist

> comments works fine, though.

If I were you, I'd check this after each and every upgrade. And I'd
check it after each full moon, too.

There's an lwall quote that perfectly describe things like this:

"I find this a nice feature but it is not according to the
documentation.
    Or is it a BUG?"
"Let's call it an accidental feature. :-)" Larry Wall in
<6909 at jpl-devvax.JPL.NASA.GOV>

Arnt
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Confidentiality Statement:
Confidentiality Statement:

This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.