[p4] p4 protect -- order of entries - Russell C. Jackson - com.perforce.perforce-user

7 messages in com.perforce.perforce-user[p4] p4 protect -- order of entries

From	Sent On	Attachments
Matthew Goos	16 Nov 2001 10:47
Mike Castle	16 Nov 2001 11:28
Russell C. Jackson	16 Nov 2001 11:44
Matthew Goos	16 Nov 2001 13:12
Mike Castle	16 Nov 2001 13:39
Ken Wilson	16 Nov 2001 13:43
Russell C. Jackson	16 Nov 2001 17:53

Subject:	[p4] p4 protect -- order of entries
From:	Russell C. Jackson (rcja...@alum.atu.edu)
Date:	11/16/2001 11:44:53 AM
List:	com.perforce.perforce-user

Hi Matthew,

What Mike showed you below is correct, but what he didn't tell you was that the way you wrote it will NOT work. The list is processed from top down, so the entry to read the whole depot overrides the entry to remove it from the people directory in your example.

Rusty

-----Original Message----- From: perf...@perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Mike Castle Sent: Friday, November 16, 2001 11:29 AM To: 'perforce-user at perforce.com' Subject: Re: [p4] p4 protect -- order of entries

On Fri, Nov 16, 2001 at 10:48:09AM -0800, Matthew Goos wrote:

I am creating 'people' directories for our users. I want each user to see only his/her directory and no one else's. Is this the proper order for my protect file?

read group p4users -//depot/people/... //denies access -- Will this override the others?? read group p4users * //depot/... //grants read access to everything else read group p4users * //depot/people //limits the view write <user> * //depot/people/<user>/... //grants specific access

What about the following:

read group p4users * //depot/... read group p4users * -//depot/people/... write user <user> * //depot/people/<user>/...

Though I might replace the second line with: read user * * -//depot/people/...

For more explicit privacy.