P4DEBUG

Perforce 2003.2 Command Reference


<< Previous Chapter P4CONFIG	Table of Contents Index Perforce on the Web	Next Chapter >> P4DIFF

P4DEBUG

Description

Set Perforce server or proxy trace flags.

Usage Notes

Used by
Client?
Used by
Server?
Command-Line Alternative
Can be set in P4CONFIG file?

No

Yes

None

No

Used by Client?	Used by Server?	Command-Line Alternative	Can be set in P4CONFIG file?
No	Yes	None	No

Value if not Explicitly Set

Operating System
Value

All

If not set, this variable is not used.

Operating System	Value
All	If not set, this variable is not used.

Examples

`server=1`

server=2

server=3

`server=1`
server=2
server=3

Notes

In most cases, the Perforce server trace flags are useful only to administrators working with Perforce Technical Support to diagnose or investigate a problem.

The preferred way to set trace flags for the Perforce server (or proxy) is to set them on the p4d (or p4p) command line. For technical reasons, this does not work for sites running Perforce servers or proxies as services under Windows. Administrators at such sites can use p4 set to set the trace flags within P4DEBUG, allowing the NT service to run with the flags enabled.

Some server debug levels require specific server release levels.

For further information, see the Perforce System Administrator's Guide.

Perforce 2003.2 Command Reference


<< Previous Chapter P4CONFIG	Table of Contents Index Perforce on the Web	Next Chapter >> P4DIFF

P4DEBUG

Description

Usage Notes Used by Client? Used by Server? Command-Line Alternative Can be set in P4CONFIG file? No Yes None No

Value if not Explicitly Set Operating System Value All If not set, this variable is not used.

Examples server=1 server=2 server=3

Notes

Usage Notes

Used by
Client?
Used by
Server?
Command-Line Alternative
Can be set in P4CONFIG file?

No

Yes

None

No

Value if not Explicitly Set

Operating System
Value

All

If not set, this variable is not used.

Examples

`server=1`

server=2

server=3