Server startup commands

You can configure Helix Server to automatically run commands at startup using the p4 configure as follows:

p4 configure set "servername#startup.n=command"

Where n represents the order in which the commands are executed: the command specified for startup.1 runs first, then the command for startup.2, and so on. See startup.N in Helix Core Command-Line (P4) Reference.

Key startup commands include p4 pull and p4 journalcopy.

The following example specifies:

• one pull thread for metadata
• three parallel pull threads, each for a different range of file sizes, where the pull interval is 1 second for small files and 3 seconds for large files
• updating the LDAP groups every 30 seconds:

startup.1=pull -i 1
startup.2=pull -u -i 1  --batch=1000 --min-size=1 --max-size=2047
startup.3=pull -u -i 2  --batch=10 --min-size=2048 --max-size=4096
startup.4=pull -u -i 3  --batch=5 --min-size=4097
startup.5=ldapsync -g -i 1800

Additional commands you might consider are p4 cachepurge, p4 bgtask, and p4 ldapsync.

Server options to control metadata and depot access

When you start a replica that points to a master server with P4TARGET, set the configurables db.replication (access to metadata) and lbr.replication (access the depot’s library of versioned files) to control which Helix Server commands are permitted or rejected by the replica server