pcp
[Top] [All Lists]

Re: --prefix does not work.

To: Brian Harvell <harvell@xxxxxxx>
Subject: Re: --prefix does not work.
From: Mark Goodwin <markgw@xxxxxxx>
Date: Fri, 24 Aug 2001 14:44:43 +1000 (EST)
Cc: Mark Goodwin <markgw@xxxxxxx>, Ken McDonell <kenmcd@xxxxxxxxxxxxxxxxx>, pcp@xxxxxxxxxxx
In-reply-to: <Pine.GSO.4.33.0108231520570.3242-200000@boondoggle.office.aol.com>
Sender: owner-pcp@xxxxxxxxxxx
On Thu, 23 Aug 2001, Brian Harvell wrote:

> On Mon, 20 Aug 2001, Mark Goodwin wrote:
> >
> > Perhaps we weren't clear enough: PCP does not use --prefix in the
> > configure part of the build because PCP requires multiple points of
> > relocation but --prefix only provides one, rendering --prefix useless.
> >
> > The correct way to relocate PCP directories is to change
> > src/include/pcp.conf.in. If you still disagree, then you must know
> > something about --prefix that we are missing, so fix it and send me
> > a patch!
> >
> 
> If you just use prefix it uses the defaults and you can't split it. However,
> you can have a more fine grained control by specifying libdir localstatedir
> etc. I've attached a patch that will allow you to do this. It's a little bit 
> of
> a kludge but it works. If you don't specify anything it works as before. This
> patch also fixes a few typos that prevent even modifying pcp.conf.in from
> working correctly (hard coded paths and pulling the wrong config var)

thanks for the patch. I'm going to split it into two : first to fix the
incorrect/hardcoded paths, and then second for your --prefix changes.
The existing pcp.conf mechanism cannot be deprecated without breaking
IRIX compatibility and we're not willing to do that. However, we should
be able to accommodate your changes for rewriting src/include/pcp.conf.in.

> 
> Personally I think the old directory structure could just go away. I didn't
> like it in the Irix day and it's even worse in a gnu environment.

Why you don't like it?

> 
> On another note anyone know if there are any hardware monitoring pmdas? I'm
> looking to be able to detect when things like disk, memory, cpus etc go bad.
> 

try the "lmsensors" PMDA, contributed by Troy Dawson (dawson@xxxxxxxx).
This will allow you to monitor fans, voltages, etc on your motherboard
(if your h/w supports it). Also, the "roomtemp" PMDA exports the room
temperature from one or more sensors built using the DS2480 and DS1280
chipsets and MicroLAN technology from Dallas Semiconductor. As for detecting
failed h/w, you might get somewhere with a syslog dredger of some kind
(we have a PMDA for this called "logtail", but it's not part of the
open source package).

The lmsensor and roomtemp PMDAs were both shipped with pcp-2.2.1-3,
get it from ftp://oss.sgi.com/projects/pcp/download/

-- Mark


<Prev in Thread] Current Thread [Next in Thread>