Perforce 2003.2 System Administrator's Guide
<< Previous Chapter
Perforce Server (p4d) Reference
Table of Contents
Index
Perforce on the Web


Index

A

access level
and protections    
access levels    
admin access level      
administrator
force flag    
privilege required    
administrators
and job specifications    
allocating disk space    
AppleSingle    
arguments
passing to triggers    
.asp files    
automated checkpoints    
automating Perforce    
.avi files    

B

backing up    
backup
procedures    
recovery procedures    
backups
and Perforce Proxy    
.bmp files    
branches
namespace    
.btr files    
buffering
of input/output in scripts    

C

can    
case-sensitivity
and cross-platform development    
UNIX and Windows      
change review    
changelist numbers
highest possible    
pending vs. submitted changelists    
changelists
deleting    
editing    
validating    
checkpoint
as part of backup script    
creating    
creation of, automating    
defined    
ensuring completion of    
failed    
introduced    
managing disk space    
when to call support    
checkpoints
creating with p4 admin      
client
and port    
clients
namespace    
.cnf files    
commands
forcing    
counter
limits    
CPU
and performance    
CR/LF conversion    
creating checkpoints    
creating users    
creation of users
preventing    
cross-platform development
and case sensitivity    
.css files    

D

daemon
change review    
daemons        
changelist numbers    
creating    
database files    
defined    
where stored    
db.* files    
debugging
with server tracing    
defect tracking
integrating with Perforce    
deleting
changelists    
depots    
files, permanently    
user groups    
deleting users    
depot
and Mac file formats    
and server root    
depot files
see versioned files    
depots
defined    
defining    
deleting    
listing    
local    
mapping field    
multiple    
namespace    
remote      
remote, defining    
disabling journaling    
disk
performance    
sizing    
disk space
allocating    
and server trace flags    
freeing up    
required for upgrade    
distributed development    
DNS
and performance      
.doc files    
.dot files    
drives
and db.*and journal file    

E

editing
changelists    
editor
Wordpad, limitation    
environment variables
P4PCACHE      
P4PORT    
P4TARGET      
error logging    
error messages
and p4 verify    
example
specifying journal files    
exclusionary mappings
and protections    
.exp files    

F

fields
of job template    
file formats
AppleSingle    
file names
mapping to file types    
file specification
and protections    
file types    
mapping to file names    
files
access to, limiting    
.asp    
.avi    
.bmp    
.btr    
.cnf    
.css    
database    
.doc    
.dot    
.exp    
.gif    
.htm    
.html    
.ico    
.inc    
.ini    
.jpg    
.js    
left open by users, reverting    
.lib    
.log    
matching Perforce file types to file names    
.mpg    
.pdf    
.pdm    
permanent deletion of    
.ppt    
subscribing to    
verification of    
versioned    
.xls    
filesystems
and performance    
large    
NFS-mounted, caveats      
firewall
defined    
running Perforce through    
flags
and Perforce Proxy    
-f to force    
server, listed    

G

.gif files    
groups
and protections      
and subgroups    
deleting    
editing    
of users    

H

hostname
changing your server's    
hosts
and protections    
hosts file
on Windows and UNIX    
.htm files    
.html files    

I

-i
and inetd    
automating job submissions    
automating user creation    
.ico files    
.inc files    
inetd      
.ini files    
installing
license file    
on network drives    
on NFS filesystems      
on UNIX    
on Windows    
on Windows network drives    
Perforce Proxy    
IP address
changing your server's    
servers and P4PORT    
IP forwarding
and ssh    

J

job fields
data types    
job specification    
and administrators    
and comments    
default format    
defining fields    
extended example    
warnings    
job template
default    
fields of    
viewing    
jobs
comments in    
other defect tracking systems    
journal
defined    
introduced    
managing size of    
where to store    
journal file
specifying    
store on separate drive    
journaling
disabling    
.jpg files    
.js files    

L

label
namespace    
.lib files    
license    
licensing information    
limitations
on information passed to triggers    
Wordpad    
list access level    
listing
depot names    
local depots    
log file
specifying    
.log files    

M

Mac
and file formats    
Macintosh
OS X    
mappings
and depots    
maxresults
and multiple groups    
and P4Win    
and performance    
use of    
maxscanresults
and performance    
use of    
maxscanrows
and multiple groups    
and P4Win    
MD5 signatures    
memory
and performance    
requirements    
metadata
see database files      
monitoring server activity    
moving servers    
across architectures    
between Windows and UNIX    
new hostname    
new IP address    
same architecture    
.mpg files    
multiple depots    
multiple triggers
on one file    

N

naming
depots    
network
and performance      
Perforce Proxy configuration    
problems, diagnosing    
network drives
and triggers    
and Windows    
network interface
directing server to listen to specific    
NFS
and installation      
non-forking    

O

obliterating files    
open access level    
operating systems
and large filesystem support    
OS X
and UNIX    

P

p4 admin
and Windows      
creating checkpoints      
stopping server with        
p4 jobspec
warnings    
p4 monitor    
p4 set -s
setting variables for Windows services    
p4 triggers
form    
p4 typemap    
p4 verify    
use of    
p4d
-f option, and triggers    
flags, listed    
security      
specifying journal file    
specifying log file    
specifying port    
specifying server root    
specifying trace flags    
p4d.exe    
P4DEBUG    
and proxy server    
P4JOURNAL    
P4LOG    
and proxy server    
P4P
and remote development    
see Perforce Proxy      
P4PCACHE      
P4PORT
and client    
and proxy server    
and server      
IP addresses and your server    
Perforce Proxy    
P4ROOT      
and depot files    
p4s.exe    
P4TARGET      
passwords
setting      
PDF files
and p4 typemap    
.pdf files    
.pdm files    
Perforce
uninstalling    
Perforce clients
and P4PORT    
Perforce file types    
Perforce Proxy      
backups    
diskspace usage    
installation    
options    
protections    
startup    
stopping    
troubleshooting    
tuning    
Perforce server
and P4PORT    
and triggers    
and Windows network drives    
installing under NFS      
monitoring    
moving to another machine    
running from inetd    
UNIX upgrade    
upgrading    
upgrading under Windows    
verifying    
vs. service    
Perforce service
vs. server    
perforce.exe    
performance
and memory    
and scripts    
and wildcards under Windows    
CPU    
monitoring    
network      
preventing server swamp    
slow, diagnosing    
performance tuning
and Perforce Proxy    
permissions
see protections    
port
for client    
for server    
specifying    
ports
running out of TCP/IP    
.ppt files    
pre-submit triggers
see triggers    
privileges
administrator    
protections      
algorithm for applying    
and commands    
and groups    
and Perforce Proxy    
and performance    
and superusers    
commands affected by    
default    
exclusionary    
multiple    
schemes for defining    
securing remote depots    
protections table    
proxy    
and remote development    
python    

R

RAM
and performance    
read access level    
recovery
procedures    
remote depots    
and virtual users    
defining    
securing    
resetting passwords    
review access level    
review daemon    
revision range
and obliterate    
rich text
and p4 typemap    
root
must not run p4d      

S

scripting
buffering standard in/output    
guidelines for efficient    
with -i    
scripting Perforce      
secure shell    
security
and passwords    
p4d must have minimal privileges      
preventing user impersonation    
restrict remote access    
server
and triggers    
backing up    
forking, and triggers    
license file    
licensing    
migrating    
monitoring    
port    
proxy    
recovery    
root, specifying    
running from inetd    
running in background    
running single-threaded    
specifying journal file    
specifying log file    
specifying port    
stopping on Windows    
stopping with p4 admin        
trace flags    
upgrading    
verifying    
vs. service    
Windows    
server flags
listed    
server root
and depots    
and P4ROOT    
creating    
defined    
specifying    
server upgrade
UNIX    
Windows    
setting passwords      
single-threaded    
ssh    
standard input/output
buffering    
stopping server
on Windows    
with p4 admin        
subgroups
and groups    
submission, validating    
super access level      
superuser
and triggers    
force flag    
Perforce, defining    
superusers
and protections    
svcinst.exe    
symbolic links
and disk space    

T

TCP/IP
and port number    
running out of ports    
technical support
when to call    
template
job, default    
trace flags
specifying    
triggers      
and Windows    
arguments, passing to    
defined    
form    
multiple, on one file    
naming    
ordering    
script, specifying arguments to    
security and p4d      
server must be able to fork    
single, on multiple filespecs    
troubleshooting
Perforce Proxy      
slow response times    
type mapping    

U

umask(1)    
unicode    
uninstalling Perforce    
UNIX
/etc/hosts file    
and case-sensitivity    
upgrading a server    
upgrading
server    
users
access control by groups    
and protections    
creating    
deleting    
files, limiting access to    
nonexistent    
preventing creation of    
preventing impersonation of    
resetting passwords    
virtual, and remote depots    

V

validation, of changelists    
variables
setting for a Windows service    
verifying server integrity    
version information
and Perforce Proxy    
clients and servers    
versioned files    
defined    
format and location of    
introduced    
where stored    
view
scope of, and performance    

W

warning
security    
warnings
and job specifications    
database changes on upgrade      
disk space and Perforce Proxy    
disk space and upgrade    
obliterating files    
security and p4d      
wildcards
and protections    
and Windows performance    
Windows
and case-sensitivity      
and p4 admin    
and server upgrade    
hosts file    
installer    
installing on network drive      
server    
service, setting variables in    
stopping server    
triggers and network drives    
Wordpad
limitation    
wrappers    
write access level    

X

.xls files    

Perforce 2003.2 System Administrator's Guide
<< Previous Chapter
Perforce Server (p4d) Reference
Table of Contents
Index
Perforce on the Web
Please send comments and questions about this manual to [email protected].
Copyright 1999-2003 Perforce Software. All rights reserved.
Last updated: 12/12/03