qa/828 - pander to more valgrind non-determinism

This time, the i836 version on openSuSE 12.1.
Merge branch 'dev' of git://git.performancecopilot.org/pcp/pcp into dev
Typo in __pmLogLoadLabel(): '0' --> '\0'

Caused no incorrect behaviour, but did cause the list of
compressed file suffuxes to be traversed unnecessarily.
Merge remote-tracking branch 'origin/dev' into brolley/dev
Fix pmLogIndom record description in pcp-archive(5).

All instance numbers are grouped together first followed by
all the offsets into the string table.
pmprobe - improve guard in error case

If the context is valid, but access controls prevent fetching
information from pmcd, then the number of metrics found in a
PMNS traversal may be 0.  Avoid calling pmLookupName() in this
case.
libpcp - extra diagnostics

In the areas of pmcd connection mode selection and user/group
authorisation.
libpcp - non-secure handshake changes

User and/or group authorisation requires the non-secure implementation
of __pmSecureServerHandshake() to accept the PDU_FLAG_CREDS_REQD
credential, provided the connection has been made with a unix domain
socket.
qa/944 - extensions

1. run pmcd and clients with more diagnostic ... syphon this output
   into 944.full
2. add another test to be sure the implementation of user and
   authentication, fails when the connection to pmcd is via
   a unix domain socket ... but only try this for platforms that
   do NOT have secure socket support (see the comment in 944 for
   more details)
3. add variant output files for the have/do not have secure sockets
   cases
qa/admin/myconfigure - adjust configure options to match logic in Makepkgs
qa/admin/show-me-all - fix small botch in hostname for echo
Merge branch 'dev' of git://git.pcp.io/kenj/pcp into dev
pmdagluster: thread-based timeout for too-long gluster query

glusterfs commands taking a while during dusruptive events is
definitely not "social".  To work around the issue, I updated
the gluster pmda to place the vol info and profile commands
into a separate thread, with a timeout.

I've also added a log record showing when the timeout triggers
[Mon Oct 20 09:52:21] pmdagluster(5264) Info: Gluster command (gluster --xml volume profile repl info) took too long to respond, triggering timeout

Now with the same scenario, the agent doesn't get terminated by
pmcd and you can see the self heal process kick into life quite
well.
build: update gitignore file for systemd pmda
pmdalinux: add hinv.{cpu,node}.online metrics

New metrics added exporting state from sysfs, exercised
via qa/747.  Also fixed a couple of help text typos and
missing hinv.cpu entries while in the neighbourhood.