New 2000.1 Features

Please Give Us Feedback

Installing Perforce on UNIX

Creating a Perforce server root directory

Telling the Perforce server which port to listen to

Telling Perforce clients which port to talk to

Starting the Perforce server

Stopping the Perforce server

Installing Perforce on NT

Terminology note: NT services and servers

Starting and stopping Perforce on NT

Upgrading a Perforce Server

UNIX Upgrades

Upgrading from UNIX Release 98.2 or later

Upgrading from UNIX Release 98.1

Upgrading from UNIX Release 97.3

Upgrading from a pre-97.3 UNIX release

NT upgrades

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 diskspace for anticipated growth

Managing disk space after installation

Large filesystem support

UNIX: Install servers on non-NFS filesystems

NT: Username and password required for networked drives

UNIX and NT: Run p4d as a non-privileged user

Logging errors

Case-sensitivity issues

Tune for performance

Backup and Recovery Concepts

Checkpoint files

Creating a Checkpoint

Journal files

Enabling Journaling

Disabling Journaling

Versioned files

Versioned File Formats

Back up after checkpointing

Backup Procedures

Recovery Procedures

Database corruption, versioned files unaffected

To recover the database

Check your system

Your system state

Both database and versioned files lost or damaged

To recover the database

To recover your versioned files

Check your system

Your system state

Ensuring system integrity after any restoration

Basic Perforce Administration

Resetting user passwords

Creating new users

Preventing creation of new users

Reverting files opened by obsolete users

Reclaiming diskspace by obliterating files

Deleting changelists and editing changelist descriptions

File verification by signature

Verifying during server upgrades

Defining filetypes with p4 typemap

Forcing operations with the -f flag

Advanced Perforce Administration

Running Perforce through a firewall

Secure shell

Solving the problem

Specifying IP addresses in P4PORT

Running from inetd on UNIX

Case-sensitivity and multi-platform development

Perforce server on UNIX

Perforce server on NT

Perforce server trace flags

Migrating to a new machine

Moving your versioned files and Perforce database

Between machines of the same architecture:

Between different architectures using the same text format:

Between NT and UNIX:

Changing the IP address of your server

Changing the hostname of your server

Using Multiple Depots

Remote depot notes

When and when not to use remote depots

Restrictions on remote depots:

Defining new depots

Define the default depot

Defining local depots

Defining remote depots

The Map: field

Other depot operations

Naming depots

Listing depots

Deleting depots

Limiting access from other servers

Users working with multiple depots

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

The Default Perforce Job Template

The Job Template's Fields

The Fields: Field

Caveats, Recommendations, and Warnings

The Preset-fieldname: Fields

The Values-fieldname: Fields

The Comments: Field

Example: Perforce's Custom Template

Integrating with Other Defect Tracking Systems

Caveats, Warnings and Recommendations

Triggers

Using triggers

Triggers and security

Daemons

Perforce's change review daemon

Creating other daemons

Commands used by daemons

Daemons and counters

Scripting and buffering

Tuning for Performance

Memory

Filesystem performance

Diskspace 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"

Maxresults for users in multiple groups

Scripting efficiently

Iterating through files

Using list input files

Using branch views

Limiting label references

The temporary client trick

Checkpoints for Database Tree Rebalancing

Using the Perforce installer

Upgrade notes

Installation options

User install

Administrator typical

Administrator custom

Uninstall Perforce

NT services vs. NT servers

Starting and stopping the Perforce NT service

Starting and stopping the Perforce NT server

Installing the Perforce NT service on a network drive

Multiple Perforce services under NT

NT configuration parameter precedence

Resolving NT-related instabilities

Users having trouble with P4EDITOR or P4DIFF

Synopsis

Syntax

Description

Exit Status

Options

Usage Notes

Related Commands

All rights reserved.

Perforce software and documentation is available from http://www.perforce.com. You may download and use Perforce programs, but you may not sell or redistribute them. You may download, print, copy, edit, and redistribute the documentation, but you may not sell it, or sell any documentation derived from it. You may not modify or attempt to reverse engineer the programs.

Perforce programs and documents are available from our Web site as is. No warranty or support is provided. Warranties and support, along with higher capacity servers, are sold by Perforce Software.

Perforce Software assumes no responsibility or liability for any errors or inaccuracies that may appear in this book.

By downloading and using our programs and documents you agree to these terms.

Perforce and Inter-File Branching are trademarks of Perforce Software. Perforce software includes software developed by the University of California, Berkeley and its contributors.

All other brands or product names are trademarks or registered trademarks of their respective companies or organizations.