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, and if countername does not already exist, it is created.

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.

You can enable or disable server process monitoring by setting the monitor counter to 1 or 0. You must stop and restart the Perforce server for this change to take effect. Once process monitoring is enabled, you can use p4 monitor to observe processes spawned by the Perforce server.

To configure password strength requirements or to require the use of the ticket-based authentication mechanism, set the security counter. See the System Administrator's Guide for details.

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.
-f monitor [ 1 | 0 ]	Activate or deactivate server process monitoring. See p4 monitor for details.
-f security [ 0 | 1 | 2 | 3 ]	Set the server security level. See the System Administrator's Guide for details.
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
• Counters are represented internally as signed ints. (For most platforms, the largest value that can be stored in a counter is 2³¹ - 1, or 2147483647. A server running on a 64-bit platform can store counters up to 2⁶³ - 1, or 9223372036854775807)

Examples

p4 counter mycounter 123	Set the value of a counter mycounter to 123. If mycounter does not exist, it is created. Requires review access.
p4 counter mycounter	Display the value of mycounter. If mycounter does not exist, its value is displayed as 0. Requires list access.

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