Perforce SysAdmin
Install and Upgrade
- Getting Perforce
- Installing Perforce
- Download the files and make executable
- Perforce server root directory
- Perforce server port
- Telling Perforce client programs which port to talk to
- Starting the Perforce server
- Stopping the Perforce server
- Installation and Administration Tips
- Release and license information
- Observe proper backup procedures
- Use separate filesystems for server root and journal
- Use protections and passwords
- Allocate disk space
- Managing disk space after installation
- Large filesystem support
- NFS support
- Run p4d as a non-privileged user
- Logging errors
- Case sensitivity issues
- Tune for performance
Backup and Recovery
- Backup and Recovery Concepts
- Checkpoint files
- Journal files
- Versioned files
- Backup Procedures
- Recovery Procedures
- Database corruption, versioned files unaffected
- Both database and versioned files lost or damaged
- Ensuring system integrity after any restoration
Superuser Tasks
- Basic Perforce Administration
- Resetting user passwords
- Creating new users
- Preventing creation of new users
- Deleting obsolete users
- Reverting files left open by obsolete users
- Reclaiming disk space by obliterating files
- Deleting changelists and editing changelist descriptions
- File verification by signature
- Defining filetypes with p4 typemap
- Forcing operations with the -f flag
- Advanced Perforce Administration
- Running Perforce through a firewall
- Specifying IP addresses in P4PORT
- Running from inetd on UNIX
- Case sensitivity and multi-platform development
- Perforce server trace flags
- Migrating to a new machine
- Moving your versioned files and Perforce database
- Changing the IP address of your server
- Changing the hostname of your server
- Using Multiple Depots
- Remote depot notes
- Defining new depots
- Other depot operations
- Limiting access from other servers
- Users working with multiple depots
Protections
- When Should Protections Be Set?
- Setting Protections with "p4 protect"
- The permission lines' five fields
- Access levels
- Which users should receive which permissions?
- Default protections
- Interpreting multiple permission lines
- Exclusionary protections
- Granting Access to Groups of Users
- Creating and editing groups
- Groups and protections
- Deleting groups
- How Protections are Implemented
- Access Levels Required by Perforce Commands
Job Specifications
- The Default Perforce Job Template
- The Job Template's Fields
- The Fields: field
- The Presets: field
- The Values: fields
- The Comments: field
- Caveats, Warnings, and Recommendations
- Example: A Custom Template
- Working with third-party defect tracking systems
- Using P4DTI - Perforce Defect Tracking Integration
- Building your own integration
- Getting more information
Daemons and Triggers
- Triggers
- Using triggers
- Triggers and security
- Triggers and Windows
- Daemons
- Perforce's change review daemon
- Creating other daemons
- Commands used by daemons
- Daemons and counters
- Scripting and buffering
Performance
- Tuning for Performance
- Memory
- Filesystem performance
- Disk space allocation
- Network
- CPU
- Diagnosing Slow Response Times
- Hostname vs. IP address
- Try p4 info vs. P4Win
- Windows wildcards
- DNS lookups and the hosts file
- Location of the "p4" executable
- Preventing Server Swamp
- Using tight views
- Assigning protections
- Limiting "maxresults"
- Scripting efficiently
- Checkpoints for Database Tree Rebalancing
Perforce and Windows
- Using the Perforce installer
- Upgrade notes
- Installation options
- Windows services vs. Windows servers
- Starting and stopping the Perforce service
- Starting and stopping the Perforce server
- Installing the Perforce service on a network drive
- Multiple Perforce services under Windows
- Windows configuration parameter precedence
- Resolving Windows-related instabilities
- Users having trouble with P4EDITOR or P4DIFF
Perforce Server (p4d) Reference
- Synopsis
- Syntax
- Description
- Exit Status
- Options
- Usage Notes
- Related Commands
Index