Jump to content

Dave Foglesong

Member Since 22 Sep 2014
Offline Last Active Yesterday, 08:39 PM

Posts I've Made

In Topic: replica: switch between read-only and forward?

05 September 2019 - 05:37 PM

There used to be a rpl.forward.all configurable that had to be set for forwarding replicas. It's not listed in the docs for the more recent versions (which normally would imply it's been deprecated) but it's still in the "p4 help configurables" output in my 19.1 test server so I'm not sure what the status of this configurable is in the current version. But depending on what version of p4d you're running, you might need to set this.

In Topic: How can we avoid integrating changes from one branch to other in perforce?

03 July 2019 - 03:59 PM

It depends on the exact requirements you're working with, but removing "=branch" permissions might be an option. From "p4 help protect":

=branch - if this right is denied, users are not
  permitted to use files as a source
  for 'p4 integrate'

So if you remove =branch permission from the testing branch, that will prevent integrations to other branches. e.g., something like this in the protect table:

write user * * //depot/...
=branch user * * -//depot/testing/...

Will prevent users from running "p4 integrate //depot/testing/... //depot/main/..."

But note that this prevents ALL integrations from testing -- not just to main, but to all other branches as well. If that's OK, this might work for you. But if you need to allow integrations from testing to other branches, then you'd need to write a broker filter script (if you're using a broker) or a trigger.

In Topic: How to get rid of security enabled and LDAP requirement?

20 June 2019 - 03:36 PM

You can adjust the configuration settings directly with p4d (you don't need to start the server), see this KB:

"Accessing Server Configuration Variables"

This should let you change the auth.default.method from LDAP to Perforce, and lower the security setting.

And if you weren't already aware of this, if you delete db.protect it clears all protections so the next person who runs "p4 protect" has super access. You may need to do this to grant your new account super access.

"Regaining Super User Access to Your Perforce Database"

In Topic: p4 sync not behaving as expected. What am I doing wrong?

01 June 2019 - 06:29 AM

The command above has a space between the "..." and "#head". If that's actually what you're running, that's passing two paths to the sync command -- so it's syncing "C:\Etc\dev\work\libjpeg/..." and then it's syncing your entire workspace to "#head".

If you remove the space it will do what you want. But since #head is the default rev to sync to ("p4 sync -f //some/path/..." and "p4 sync -f //some/path/...#head" do the same thing), you don't really need the "#head" rev specification here.

In Topic: Check locations of files in the Perforce depot

14 May 2019 - 06:20 PM

I don't know how expensive this would be on a very large system, but "p4 grep" would do it. Something like:

p4 grep -i -e somenamehere //depot/.../p4.protect