Mark Wagner's questions

As part of provisioning servers we run HP's Insight Diagnostics to test the hardware. This is a manual process. Is there a way automate the running of Insight Diagnostics?

There is the hpdiags software with the option "-rd:" "Run a diagnosis of all diagnosable devices." From my testing this doesn't do much (it just reads the SMART info from the disks). Has anybody had better luck with it?

Hardware: BladeCenter c7000 with HP ProLiant BL460c blades, DL360s.

OS: ESXi and Ubuntu.

Here is a zfs pool with checksum errors:

    NAME        STATE     READ WRITE CKSUM
    pool0       ONLINE       0     0    42
      c1t1d0    ONLINE       0     0    30
      c1t2d0    ONLINE       0     0    19
      c1t3d0    ONLINE       0     0    16
      c1t4d0    ONLINE       0     0    24

errors: Permanent errors have been detected in the following files:

    pool0/scratch:<0x80>

Is there a way to find which files / metadata have blocks with checksum errors?

Is there a standardized protocol how a registrar updates the NS information for a domain? For example, if, through my registrar's interface, I set the name servers for "example.com" to "ns1.example.com" and "ns2.example.com" how are [a-m].gtld-servers.net updated with this information? Does this protocol use the whois information or is that merely informational for the end user?

Edit: I see rfc3375 "Generic Registry-Registrar Protocol Requirements" but that is informational.

I work with a cfengine installation that has grown organically and become quite complicated. Some stanzas use many classes, e.g., class1&(class2|class3)&!class4|class5

Is there some tool that would take a cfengine config and simplify it, similar to the simplification of logic circuits with boolean algebra?

Failing that, are there any tools for analyzing cfengine configurations? E.g., a class and object visualization tool might be helpful.

Is it allowed to have an NS record be a CNAME? E.g.:

subdomain.example.com.       IN NS  ns1.example.com.
ns1.example.com.             CNAME  foo.example.com.
foo.example.com.             IN A   10.1.1.1

This doesn't seem to work in bind though this (of course) does:

subdomain.example.com.       IN NS  foo.example.com.
foo.example.com.             IN A   10.1.1.1

Any pointers to RFCs prohibiting this setup would be appreciated.