p4d server
E697461
The p4d server is Perforce's core version control server process that manages repositories, file revisions, and client interactions in the Helix Core system.
Statements (53)
| Predicate | Object |
|---|---|
| instanceOf |
Perforce Helix Core component
ⓘ
version control server process ⓘ |
| alsoKnownAs |
Perforce server
NERFINISHED
ⓘ
p4d ⓘ |
| communicatesWith |
Helix Core APIs and integrations
NERFINISHED
ⓘ
Helix Core GUI clients NERFINISHED ⓘ p4 command-line client NERFINISHED ⓘ |
| configurationVia |
P4CONFIG environment settings
ⓘ
p4d command-line options ⓘ server configuration tables ⓘ |
| developedBy | Perforce Software NERFINISHED ⓘ |
| handles |
client requests
ⓘ
version control operations ⓘ |
| listensOnDefaultPort | 1666 ⓘ |
| manages |
Perforce depots
ⓘ
file revisions ⓘ metadata for versioned files ⓘ |
| partOf | Helix Core NERFINISHED ⓘ |
| runsOn |
Linux
NERFINISHED
ⓘ
UNIX-like operating systems ⓘ Windows NERFINISHED ⓘ macOS NERFINISHED ⓘ |
| stores |
branches
ⓘ
changelists ⓘ job data ⓘ labels ⓘ |
| storesDataIn | Perforce database files ⓘ |
| storesVersionedFilesIn | depot storage ⓘ |
| supportsAuthenticationMethod |
SSO integration
ⓘ
password-based authentication ⓘ ticket-based authentication ⓘ |
| supportsFeature |
access control lists
ⓘ
atomic changelists ⓘ distributed versioning ⓘ file locking ⓘ proxy and edge servers ⓘ replication ⓘ shelving ⓘ streams ⓘ triggers ⓘ |
| supportsOperation |
branch
ⓘ
integrate ⓘ label ⓘ merge ⓘ shelve ⓘ submit ⓘ sync ⓘ |
| usedBy |
game development studios
ⓘ
large-scale enterprise projects ⓘ software development teams ⓘ |
| usedFor |
digital asset management
ⓘ
source code management ⓘ |
| usesProtocol | Perforce proprietary protocol ⓘ |
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.