I'd appreciate a review of the pmcd rc script, especially the container
behaviour at the end of the "start" case ... not sure if this should just be
for the initial invocation, or the recursive ones as well (current code does
the former, previous code did the latter but with possible race condition
side-effects!).
Changes committed to git://git.pcp.io/kenj/pcp master
Ken McDonell (4):
qa/338 qa/530: do not work within 2 days of a timezone change
rpm spec files: add Requires: perl(LWP::UserAgent) for activemq PMDA
package
qa/admin/check-vm: add helpful rpm perl module syntax
src/pmcd/rc_pmcd: be more careful with auto-install/-remove
build/rpm/fedora.spec | 1 +
build/rpm/pcp.spec.in | 1 +
qa/338 | 12 ++++++++++++
qa/530 | 12 ++++++++++++
qa/admin/check-vm | 32 ++++++++++++++++----------------
src/pmcd/rc_pmcd | 46 ++++++++++++++++++++++++++++++++--------------
6 files changed, 74 insertions(+), 30 deletions(-)
Details ...
commit 5207cc049e05bab020168705340689c8db525169
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue Oct 6 16:13:27 2015 +1100
src/pmcd/rc_pmcd: be more careful with auto-install/-remove
Since _pmda_setup is run in the background, and this may cause
the "rc" script to be run again (sort of recursively), it is
important to avoid race conditions here.
commit 079214b28e39ed6817197f320728e6ac8f7f170f
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue Oct 6 12:06:37 2015 +1100
qa/admin/check-vm: add helpful rpm perl module syntax
Thanks to Frank's tip, we can use the Perl module name and
ask rpm/zypper to install the appropriate package ... so
add that to the hints field as required.
commit 015d713c71b814251e95f5e0ab9a3818c915a4b1
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue Oct 6 07:00:36 2015 +1100
rpm spec files: add Requires: perl(LWP::UserAgent) for activemq PMDA package
commit cc6d5606318f9238283d776a04aacd16cac0244b
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue Oct 6 06:30:05 2015 +1100
qa/338 qa/530: do not work within 2 days of a timezone change
Conditionally notrun for the twice a year failure scenarios
seen with these tests.
|