Added perfevent PMDA to build structure.
Lock file path is now obtained from the environment.
Add man page for config file. Don't create DSO build.
perfevent is now built as a seperate RPM.
Added environment variables to proc pmda. Fixed -A flag.
Add cpusallowed metric to linux_proc
Merge perfevent PMDA source into PCP dev branch.
Added tests for perfevent PMDA
Added missing test configuration file.
Added another missing file.
Forgot to update the expected output with the new test ids.
Allow the testharness to work properly if the perfevent PMDA is not built.
Don't use bash extensions in a borne shell script.
Ensure tests are independent of the number of CPUs present on the test
host.
qa/003: hinv.node.online not always available, add to filter
qa/752: tidy up output from rtimetest.c

Previous commit made the formatting harder to read which was the exact
opposite of the intention.

The "Tuesday" bug remains unresolved at this point in time.
Merge branch 'perfeventpmda' of https://github.com/ubccr/pcp into dev
qa: remove a superflous trap in ds390log test
perfevent pmda: updates, latest code/build/qa conventions mainly

Just small stuff on (re)review of the perfevent pmda:
- use the same configure enabling conventions as for other pmdas
- makefiles no longer need LSRCFILES (unused, culled)
- use the configured library paths
- use the configured lex
- add new package into the fedora spec as well
- rpm spec %config annotation for perfevent.conf file
- fix an open-coded distro-specific path (using pmGetConfig(3), which
  also honours env overriding, so simplify a little).
- ensure $status is set correctly in qa/756, since we exit with that
- rework 757 (was triggering Kens new "failed permissions check" for
  pmcd.conf) to use the common agent install routines
buildrules: need rm -f before ln -s

In the build this was hidden because the alternate named python and
perl files did not exist.

But the same rule is used in qa/src and there the targets may exist
and it was only a matter of time before this bit somone ... like me
a couple of days ago.