[p4] Best way to determine if user has read access to file...

[Jeff A. Bowles]

I am not connected at the moment so take this with a grain of salt.
Logically, it would make sense that you would just say both: "-u echlinj"
and the filename. That will show you the lines in the protection table for
that user, specific to that file's path. (The interesting line is the last
one specified.)

But...... and this is a big caveat:

It doesn't take into account the groups that echlinj is in. The tool truly
seems to be for "p4 protect" debugging.

(I suppose you could first find the groups that echlinj is in, then use "p4
protects" for each one, but that is just ugly and inefficient enough for me
to want to avoid it.)

   -Jeff Bowles

On Wed, May 14, 2008 at 5:01 AM, <Jamie.Echlin at barclayscapital.com> wrote:

> Afternoon,
>
> What's the best way to determine if a user has read access to a file,
> short of logging in as them and doing fstat or whatever.
>
> Let's say my protections are set up like this:
>
>        write user echlinj * //depot/Jamgraph/...
>        write user echlinj * -//depot/Jamgraph/REL1.0/...
>
> So I have no read/write access to stuff under REL1.0. I was hoping this
> would work:
>
> > p4 -u p4admin protects -m -u echlinj
> //depot/Jamgraph/REL1.0/src/gparticle.cpp
> write
>
> However I don't have write access to that file.
>
> Without -m I get:
>
> write user echlinj * //depot/Jamgraph/...
> write user echlinj * -//depot/Jamgraph/REL1.0/...
>
> I don't really want to parse that to work out which line best matches
> the file in question. There must be a better way.
>