| Perforce 2000.2 Command Reference (2000.2.cr.1) | ||
|
<< Previous Chapter p4 users |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 where |
By default, p4 verify computes and displays the digest of each revision. If a revision is missing from the archive and therefore can't be reproduced, the revision's output line ends with MISSING!
To save MD5 fingerprints in the Perforce database, use p4 verify -u. Subsequent runs of p4 verify will compute checksums for the desired files and compare them against those stored by p4 verify -u. If the checksums differ, the output line will end with BAD!
Once stored, a digest is not re-stored unless p4 verify -v flag is used to overwrite it. p4 verify -v is generally only used to update the saved digest of archive files which have been deliberately altered outside of Perforce control by a Perforce system administrator.
|
-q |
Run quietly; only display output if there are errors. |
|
-u |
Store the MD5 digest of each file in the Perforce database if and only if no digest has been previously stored. Subsequent uses of p4 verify will compare the computed version against this stored version. |
|
-v |
Store the MD5 digest of each file in the Perforce database, even if there's already a digest stored for that file, overwriting the existing digest. |
|
See the Global Options section. |
Similarly, it is also good administrative practice to use p4 verify -q //... (to verify the integrity of your files) after restoring from backups, or immediately following any server upgrade.
If p4 verify returns errors, contact Perforce technical support.
For more about sound administrative practices, see the Perforce System Administrator's Guide.
| Perforce 2000.2 Command Reference (2000.2.cr.1) | ||
|
<< Previous Chapter p4 users |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 where |