Perforce 2003.1 Command Reference

p4 counterp4 counterSynopsisAccess, set, or delete a persistent variable.Syntaxp4 [g-opts] counter counternamep4 [g-opts] counter countername valuep4 [g-opts] counter -d counternamep4 [g-opts] counter -f [ change | job | journal | monitor [ 1 | 0 ] ]DescriptionCounters provide long-term variable storage for scripts that access Perforce. For example,the Perforce review daemon uses a counter (review) that stores the number of the lastprocessed changelist.When used in the form p4 counter countername, the value of variable countername isreturned. When p4 counter countername value is used, the value of variablecountername 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 thetypes 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 or0. You must stop and restart the Perforce server for this change to take effect. Onceprocess monitoring is enabled, you can use p4 monitor to observe processes spawned bythe Perforce server.Options-d countername Delete variable countername from the Perforce server.-f [change|job|journal] Force a change to one of three internal counters used byPerforce. Most installations rarely, if ever, need to use thisflag.-f monitor [ 1 | 0 ] Activate or deactivate server process monitoring.See p4 monitor for details.g-optsSee the Global Options section.34 Perforce 2003.1 Command Reference