Discussion:
[p4] Automating p4d -xx & p4d -xv checks
Michael Mirman
2016-07-01 11:14:08 UTC
Permalink
Does anyone know a sure shot way to check the exit codes from p4d -xx & p4d
-xv to be used in script?

Don’t trust $?
Best approach (IMHO) is to pipe the output and catch the lines that indicate inconsistencies.
We do it.

As a side note, -xx is "more interesting" than -xv.
We stopped running -xv a while ago, but keep running -xx everywhere (well, sort of everywhere - it's a different story) every night.

Furthermore, depending on the type of inconsistencies, you may decide how critical that is.
There are many, which overtime you grow numb to.
There are others, which normally never show up, and you would pay more attention to.

The -xv check, on the other hand, if it fails, your db is corrupt. By and large, a db corruption is visible before (and without) running -xv.
That's from our experience.

My 0.02
--
Michael Mirman
MathWorks, Inc.
508-647-7555
--
Please click here to see the post in its original format:
http://forums.perforce.com/index.php?/topic/4848-automating-p4d-xx-p4d-xv-checks
_______________________________________________
perforce-user mailing list - perforce-***@perforce.com
http://maillist.perforce.com/mailman/listinfo/perf
Loading...