Changes committed to git://oss.sgi.com:8090/nathans/pcp.git
VERSION.pcp | 2 -
src/pmcd/rc_pcp | 57
+++++++++++++++++++++++++++++++++--------------
src/pmdas/windows/data.c | 2 -
3 files changed, 43 insertions(+), 18 deletions(-)
commit 6b771b5558a85ef98c39f40ada98b0a20dc00350
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed Jul 18 10:54:00 2007 +1000
Append current date string to build number
commit 4b4bed0caca266bd44d0e4a84dfb53c7425e709d
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed Jul 18 10:53:14 2007 +1000
Minor cleanups to the kill-pmcd-from-chroot-build fix.
commit f2e89c0b5b1bdc4d7fcbb35fee0bda37edb3fc23
Author: Michael Newton <kimbrr@xxxxxxx>
Date: Wed Jul 18 10:38:03 2007 +1000
Patch to allow upgraded pcp to stop old pmcd
Nathan has previously pointed out that if you install the 2.7.1
over an existing installation (eg rpm -U), the new /etc/init.d/pcp
cannot stop a pre-existing instance of pmcd. This was an oversight
with
the pidfile change. While Nathan proposed just adding a fallback to
killall for this case, this was a problem for us as we have a build
system
(based on SuSE's) for building in a chroot, and the killall means
removing
the rpm from the chroot stops pcp for the whole machine. Although it
would
be preferable to uninstall --noscripts, getting this change through
SuSE
could take time, so for now, this patch assumes that if there is a
pmcd,
but no pidfile or log file, we're in a chroot. In addition, there is
now
a check that the pid in the pidfile matches that found for pmcd.
commit 496deaf54f4adeea111c71dbf3886c82897b1e63
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Fri Jul 13 10:55:05 2007 +1000
Correct the pmunits for sqlserver.buf_mgr.page_life_expectancy.
|