October 18th, 2012, 09:18 AM
It's no help, but I used to have ... but then I jumped in front of the band-wagon and got made redundant, so no more access to my scripts!
I had a pair of scripts, one that built a config file on a system when it was in a known good state, and which wrote memory size, number of CPUs, disks, mounted file systems, etc., along with the option of checking certain processes were, or were not running. The second script did much the same, but compared results.
Easy enough to parse for errors in the output of a metastat or prtdiag command, though I seem to recall prtdiag was not that useful for that. You might also want to look at what the picl daemon can produce.
The main thing is knowing what to look for! Thus you will find yourself adapting your script as things go *sproing* in new, and fun ways!
The moon on the one hand, the dawn on the other:
The moon is my sister, the dawn is my brother.
The moon on my left and the dawn on my right.
My brother, good morning: my sister, good night.
-- Hilaire Belloc