qa/365 - minor fiddle

Use no.such.host.pcp.io rather then not.a.real.host.pcp.io ... makes
it the same as the other qa tests and reduces the chance will miss
it the next time the global DNS lurches to the left.
Linux proc pmda - pmda.c - smack more PM_ERR_INST uses

These should return "No values available", not an error.
Linux proc pmda - proc_pid.c - parser rework

The parsers for /proc/<pid>/status and /proc/<pid>io were both
very brittle and in the case of /proc/<pid>/status totally broken
on at least one kernel version.
qa/744 - a little assistance for sudo and newhelp
pmstat - add pmlogger config as per man page

In the context of reworking where the pmlogger configuration files
are stored, noticed this one that was missing.

Also added qa/919 to validate the configuration and its installation.
qa - run 994 to check-n-repair permissions and ownership after each test

Following Nathan's excellent suggestion, check now runs 994 after
each test to check that key files and directories retain the ownership
and mode as at install time.  994 now also supports a --fix option that
repairs any breakage, and check uses this.

If a test breaks the permissions or modes, it is considered a failure
and the details are appended to the $seq.out.bad file.
man pages - rework pmie and pmlogger control and config files

The control files for pmie and pmlogger (used by the *_daily and
*_check scripts to determine what pmie and pmlogger instances to
start or restart) stay in $PCP_SYSCONF_DIR/pmie and
$PCP_SYSCONF_DIR/pmlogger, but these directories and the control
files are owned by root.

The search directory order for pmlogger config files (from the
-c option) that are not absolute pathnames is "." then
$PCP_VAR_DIR/config/pmlogger.  This directory is owned and writeable
by pcp, so pmlogger_check can create/recreate the config.default
file using pmlogconf.

The search directory order for pmie config files (from the
-c option) that are not absolute pathnames is "." then
$PCP_VAR_DIR/config/pmie.  This directory is owned and writeable
by pcp, so pmie_check can create/recreate the config.default
file using pmieconf.

This split allows the PCP files below /etc to all be owned by root
and moves the config files that the user "pcp" may need to create
or modify below $PCP_VAR_DIR.
pmie - rework control and config files

The control file for pmie (used by the pmie_daily and pmie_check
scripts to determine what pmie instances to start or restart)
stay in $PCP_SYSCONF_DIR/pmie, but this directory and the control
file is owned by root.

The search directory order for pmie config files (from the
-c option) that are not absolute pathnames is "." then
$PCP_VAR_DIR/config/pmie.  This directory is owned and writeable
by pcp, so pmie_check can create/recreate the config.default
file using pmieconf.
pmlogger - rework control and config files

The control file for pmlogger (used by the pmlogger_daily and
pmlogger_check scripts to determine what pmlogger instances to
start or restart) stay in $PCP_SYSCONF_DIR/pmlogger, but this
directory and the control file is owned by root.

The search directory order for pmlogger config files (from
the -c option) that are not absolute pathnames is "." then
$PCP_VAR_DIR/config/pmlogger.  This directory is owned and
writeable by pcp, so pmlogger_check can create/recreate the
config.default file using pmlogconf.
pmchart, pmview, hotproc pmda - cosmetic makefile changes

Needed so that qa/src/mkpermslist can scan the "install" lines
looking for non-standard user, group or mode settings.
qa/src/permslist - rework pmie and pmlogger control and config files

Needed to rerun qa/src/mkpermslist to recreate this list after
the makefile changes to move the control and config files around.

This file drives qa/994 (the ownership/permission checker).
debian packaging - rework pmie and pmlogger control and config files

The control files for pmie and pmlogger (used by the *_daily
and *_check scripts to determine what pmie and pmlogger
instances to start or restart) stay in $PCP_SYSCONF_DIR/pmie and
$PCP_SYSCONF_DIR/pmlogger, but these directories and the control
files are owned by root.

The search directory order for pmie (or pmlogger) config files
(from the -c option) that are not absolute pathnames is "." then
$PCP_VAR_DIR/config/pmie (or pmlogger).  These directories are
owned and writeable by pcp, so pmlogger_check can create/recreate
the config.default file using pmlogconf.

This commit contains the postinstall changes to enforce the new
rules and ease migration for upgrades.
pmstat - add pmlogger config file
qa/999 - add new expected error for proc.psinfo.cgroups
qa/admin/allow-pmlc-access & qa/admin/check-vm - pmlogger config.default moved

Track changes elsewhere to relocate config.default for pmlogger and pmie.
rpm/pcp.spec.in - tweak the save config logic

"control" is the only from /var/lib/pcp/config/pmlogger that
might need to go to $PCP_SYSCONF_DIR/pmlogger
qa - heaps - config file changes

Do a better job of saving and restoring configuration files (or
directories) in a way that (a) avoid mv across mount points, (b)
preserves the mode and ownership of the files, and (c) leaves a
named body in the directory containing the config file or directory
if the QA test aborts (so we know who to blame).

Use _save_config <pathname> to move <pathname> to <pathname>.$seq
and make <pathname> a copy that can be munged in QA.

Use _restore_config <pathname> to reverse the operation.
Merge branch 'dev' of git://git.performancecopilot.org/pcp/pcp into dev

Conflicts:
	man/html/pcpintro.html
	qa/660
qa/1009 - dodge pmconfig -L curve ball

eval `pmconfig -L` won't work when one of the values contains spaces,
like this ...
    nss_version=3.17.1 Basic ECC
qa/1009 and qa/1023 - dodge spaces in pmconfig -L output