SDP-887

daniel_ferrara (daniel_ferrara)
daniel_ferrara created this job , modified by C. Thomas Tyler
Open
mkrep.sh: Clarify which methods the script uses to determine P4TARGET.

An explanation from @Tom Tyler of how the P4MASTERPORT value is defined in mkrepo.sh:

If the -f <FromServerID> argument is used, which only applies when making a standby of
an edge server, then the P4TARGET value is the ExternalAddress configureable associated
with the given ServerID.

Otherwise, the P4MASTERPORT value defined when you do source /p4/common/bin/p4_vars N. (where
N is the SDP instance name; I can see this customer uses the default 1). Sourcing this file,
which is the correct way to load the SDP environment, causes the /p4/common/config/p4_1.vars
file to be sourced.

Customer would like this clarified in the docs themselves:

When I tested, I couldn't edit /p4/common/config/p4_1.vars file. If P4MASTERPORT was set with
localhost default, is it possible to add a request that add explanation about the P4TARGET of
replica server spec setting source?

Docs:
https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/Server/Unix/p4/common/bin/mkrep.sh

Perforce-internal: See: P4-22418
  • Details
  • Comments -
Status
Open
Project
perforce-software-sdp
Severity
C
Reported By
daniel_ferrara
Reported Date
Modified By
C. Thomas Tyler
Modified Date
Owned By
tom_tyler
Component
core-unix
Type
Feature