Verifying files by signature
Helix server
administrators can use the p4 verify
command to validate stored
MD5 digests of each revision of the named files. The signatures created
when users store files in the depot can later be used to confirm proper
recovery in case of a crash: if the signatures of the recovered files
match the previously saved signatures, the files were recovered
accurately. If a new signature does not match the signature in the
Helix server
database for that file revision,
Helix server
displays the characters filenames
BAD!
after the signature, and you should contact
Perforce
Technical Support.
We recommend that administrators perform
weekly, rather than nightly. For large installations, the verification of files:p4 verify
- takes considerable time to run
- puts the server under heavy load, which can impact the performance of other Helix server commands
Your search for returned result(s).