p4 counter

Synopsis

Syntax

Description

When used in the form p4 counter countername, the value of variable countername is returned. When p4 counter countername value is used, the value of variable countername is set to value.

The Perforce server uses three counters in the course of its regular operations: change, job, and journal. Superusers may use the -f flag to force changes to these counters. Changes to these counters are not without risk; see the Release Notes for examples of the types of situations in which manually resetting these counters might be appropriate.

Options

-d countername	Delete variable countername from the Perforce server.
-f [change|job|journal]	Force a change to one of three internal counters used by Perforce. Most installations rarely, if ever, need to use this flag.
g_opts	See the Global Options section.

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
N/A	N/A	list to display a counter's value; review to set a new value super to use the -f flag

• If a counter does not exist, its value is returned as zero; counter names are not stored in the database until set to a nonzero value.

• The last changelist number known to the Perforce server (the output of p4 counter change) includes pending changelists created by users, but not yet submitted to the depot. If you're writing change review daemons, you may also want to know the changelist number of the last submitted changelist, which is the second field of the output of the command:
  p4 changes -m 1 -s submitted

Related Commands

To list all counters and their values	p4 counters
List and track changelists	p4 review
List users who have subscribed to particular files	p4 reviews