Hi guys,
Wanted to send out my current recipe for working with installed
PCP packages, that recently arrived in the "dev" branches of the
pcp and pcp-gui git trees.
For both trees, a ./Makepkgs at the top level now produces one
additional package - pcp-testsuite and pcp-gui-testsuite. These
install the test scripts, binaries, sources, pcp archives + any
other life-support they need into the root.
Several of the pcpqa tests wish to do something (usually remote
somethings, so mainly this is for the non-local group tests) as
a well-know non-root user, specifically named "pcpqa". So the pcp
rpm creates this user, and sets her home directory to be the same
as the install point for the tests. In addition those tests want
to be able to change to sudo over to root to start/stop pmcd, and
install agents, etc. The rpm does not setup the sudo access, not
sure thats a good idea.
So, once the packages are installed:
# echo "pcpqa ALL=(ALL) NOPASSWD" > /etc/sudoers.d/pcpqa
# chmod 440 /etc/sudoers.d/pcpqa
# chown -R pcpqa.pcpqa /var/lib/pcp{,-gui}/testsuite
(be good if the rpm install could do the above..?)
# su -u pcpqa
$ cd /var/lib/pcp/testsuite
(if not there already)
$ make setup
(this can take awhile - generates archives, etc)
$ ./check -l -g local
Same sort of procedure for pcp-gui, with one extra step. Since this
runs some X applications, need to ensure pcpqa has access to your
local X server. Simplest way I found was to run "xhost +local:" - it
Works For Me (tm) on RHEL6, anyway. Then just:
$ cd /var/lib/pcp-gui/testsuite
$ make setup
$ ./check -l -g local
cheers.
--
Nathan
|