Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Server Administration Documentation | 2025.2

# Server startup commands

You can configure P4 Server to automatically run commands at startup by using the `p4 configure` command:

`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 the P4 CLI 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 minutes:

    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 and p4 bgtask.

The p4 webserver command is supported as a startup command. For example,
`p4 configure set "p4d-ohioHQ#startup.6=p4 webserver -p 1999"`

## Server options to control metadata and depot access

To control metadata and depot access:

1. Set the configurables `db.replication`, which controls metadata replication, and `lbr.replication`, which controls replication of versioned files, to define replication behavior.

2. Start the replica that points to the target server The immediately upstream server for replica servers, edge servers, standby servers, proxies and brokers. See also 'upstream server' and 'central server'. with the ``P4TARGET` environment variable.`

Your search for returned results