This is clearly a bug ...
The migrate_pcp_var_dir script that runs as a once-off post install
operation to cleans up some of the embedded path names when we moved
from /var/pcp to /var/lib/pcp (for better conformance to the FHS on
platforms where this is appropriate) contains this line
echo $name $eol >>$PCP_VAR_DIR/config/pmcd/pmcd.conf
it should be
echo "$name $eol" >>$PCP_VAR_DIR/config/pmcd/pmcd.conf
I've fixed it in the development source tree.
Thanks.
On Mon, 23 Aug 2004, Jan-Frode Myklebust wrote:
On Fri, Aug 06, 2004 at 06:37:59PM +1000, Mark Goodwin wrote:
SGI is pleased to announce the new version of Performance Co-Pilot (PCP)
open source (version 2.4.0-1) is now available for download from :
I just rebuilt and installed this on a few machines running
whiteboxlinux.org. On a machine without older pcp already installed,
it worked fine, but on machines with pcp-2.3.2-4 installed somthing
strange happened.. It seems to have expanded a '*' in the pmcd config
file.
Before the upgrade:
# cat /var/pcp/config/pmcd/pmcd.conf
# Performance Metrics Domain Specifications
#
# This file is automatically generated during the build
# Name Id IPC IPC Params File/Cmd
pmcd 2 dso pmcd_init
/var/pcp/pmdas/pmcd/pmda_pmcd.so
linux 60 dso linux_init
/var/pcp/pmdas/linux/pmda_linux.so
[access]
allow 129.177.* : fetch;
disallow * : all;
After upgrade (yum update):
# cat /var/lib/pcp/config/pmcd/pmcd.conf
# Performance Metrics Domain Specifications
#
# This file is automatically generated during the build
# Name Id IPC IPC Params File/Cmd
pmcd 2 dso pmcd_init
/var/lib/pcp/pmdas/pmcd/pmda_pmcd.so
linux 60 dso linux_init
/var/lib/pcp/pmdas/linux/pmda_linux.so
[access]
allow 129.177.* : fetch;
disallow bin boot dev etc export home Home initrd lib linuxlocal local
lost+found misc mnt net opt proc root sbin scratch tmp usr var : all;
-jf
|