Update pmdiscoverservices(3) and pmfind(1) man pages.
Merge remote-tracking branch 'origin/dev' into brolley/dev
More updates to pmfind(1) and pmdiscoverservices(3) man pages.
Fix shell quoting error and dup trap in test qa/835
pmdads389: new test (qa/825) to exercise install/remove/values
qa: add ds389 into the standard set of filters
pmdapapi: move the helptext buffer off the stack (fixes qa/914)

Move the buffer that holds the helptext path name off the stack.
This was causing problems under higher gcc optimisation levels,
when the pmdaInterface e_helptext pointer ended up spontaneously
pointing into weeds on the call to papi_internal_init().

This resolves failure of qa/914 when pmdapapi is built -O2, as
it otherwise contains pminfo/pmstore warnings of the form...
[DATE] pminfo(PID) Warning: pmdaInit: PMDA papi DSO: Unable to open help text file(s) from "": No such file or directory
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
qa: refactor some tests to share common discovery logic
pmdalinux: support for the additional nfs v4.1 operations

All NFS instance array definitions are also updated such that
the size macros are used in the definition, giving us better
compile-time checking that the values arrays (proc_net_rpc.h)
match up with the instance domains (pmda.c).

Thanks to Marko for pointing out these missing operations.
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.
Backport some recent fedora spec additions
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.