[p4] Any way to prevent directory creation? - Stephen Vance - com.perforce.perforce-user

7 messages in com.perforce.perforce-user[p4] Any way to prevent directory cre...

From	Sent On	Attachments
Wright, Richard	25 Aug 2003 11:30
Robert Duff	25 Aug 2003 12:18
Shelley L. Shostak	25 Aug 2003 12:54
David Foglesong	25 Aug 2003 13:01
Stephen Vance	25 Aug 2003 13:21
Wright, Richard	25 Aug 2003 13:41
Dave Lewis	25 Aug 2003 13:54

Subject:	[p4] Any way to prevent directory creation?
From:	Stephen Vance (ste...@vance.com)
Date:	08/25/2003 01:21:31 PM
List:	com.perforce.perforce-user

Rick --

I would be very careful messing with permissions on the server. Shelley's suggestion should work if you remove write permission *only for the depot directory and not existing subordinate directories or anything outside of the depot tree*. However, the result would result in server errors when someone tries to do that, a situation that would be less than clear to the end user.

With your protection table, rather than granting write permission to //depot/..., grant it to each of the app directory trees:

//depot/AppOne/... //depot/AppTwo/... //depot/AppThree/... //depot/AppFour/...

and grant no permissions, read permission or explicitly block permission to everything else. Let the list know if you need details on that part.

Steve

At 12:54 PM 8/25/2003 -0700, Shelley L. Shostak wrote:

Rick,

Remove write permission for the user that perforce runs as on the server.

Modifying the protection table may require lots of entries and affect performance.

Shelley

On Mon, 25 Aug 2003, Wright, Richard wrote:

Date: Mon, 25 Aug 2003 11:30:49 -0700 From: "Wright, Richard" <richardw at cobaltgroup.com> To: perforce-user at perforce.com Subject: [p4] Any way to prevent directory creation?

Is there any way to prevent users from creating new directories under a depot?

We have our depot set up something like this:

//depot/AppOne //depot/AppTwo //depot/AppThree //depot/AppFour etc.

I would like to be able to prevent users from creating new directories

under //depot without limiting their ability to add or modify files within those directories.

So, if a user tried to add a file: //depot/MySpecialApp/file.txt it would fail, since the //depot/MySpecialApp directory didn't already exist.

Is there any way to do this in the protections table, or do we need to

write a special trigger to handle it? And if we do need a special trigger, has someone already written something similar?

Rick Wright CM/Build Engineer The Cobalt Group, Inc. 2200 First Avenue South Seattle, WA 98134 <mailto:richardw at cobaltgroup.com> richardw at cobaltgroup.com www.cobaltgroup.com

p. 206.219.8382