Perforce is a commercial, proprietary revision control system developed by Perforce Software, Inc. by wiki

Installation:

Perforce requires at least two executables: the Perforce service (p4d), and at least one Perforce application (such as p4 on UNIX, orp4.exe on Windows). The Perforce service and applications are available from the Downloads page on the Perforce web site: http://www.perforce.com/downloads/complete_list Go to the web page, select the files for your platform, and save the files to disk. pics Windows installation is very easy. Config files and settings can be found and modified: [su_spoiler title="logfiles"] Enabling structured logging To enable structured logging, set the serverlog.file.N configurable(s) to the name of the file. Valid names for structured log files and the commands used to set them are shown in the following table. Note that enabling all structured logging files can consume considerable diskspace. See Structured logfile rotation for information on how to manage the size of the log file and the number of log rotations. all.csv All loggable events (commands, errors, audit, etc...)

p4 configure set serverlog.file.1=all.csv

commands.csv Command events (command start, compute, and end)

p4 configure set serverlog.file.2=commands.csv

errors.csv Error events (errors-failed, errors-fatal)

p4 configure set serverlog.file.3=errors.csv

audit.csv Audit events (audit, purge)

p4 configure set serverlog.file.4=audit.csv

track.csv Command tracking (track-usage, track-rpc, track-db)

p4 configure set serverlog.file.5=track.csv

user.csv User events; one record every time a user runs p4 logappend.

p4 configure set serverlog.file.6=user.csv

events.csv Server events (startup, shutdown, checkpoint, journal rotation, etc.)

p4 configure set serverlog.file.7=events.csv

integrity.csv Major events that occur during replica integrity checking.

p4 configure set serverlog.file.8=integrity.csv

[/su_spoiler] This also can be used for Linux version of P4