pcp
[Top] [All Lists]

Re: I find the cause of the failure in case 374

To: "Zhang, Sonic" <sonic.zhang@xxxxxxxxx>
Subject: Re: I find the cause of the failure in case 374
From: kenmcd@xxxxxxxxxxxxxxxxx
Date: Mon, 13 Jan 2003 10:22:46 +1100 (EST)
Cc: "PCP (E-mail)" <pcp@xxxxxxxxxxx>
In-reply-to: <957BD1C2BF3CD411B6C500A0C944CA2602BCF24F@xxxxxxxxxxxxxxxxxxxxx>
Reply-to: kenmcd@xxxxxxxxxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Fri, 10 Jan 2003, Zhang, Sonic wrote:

> Hi,
> 
>       I find the cause. The following script line in case 374 can't work
> properly, because the folder "/usr/share/pcp/bin", which "pmlogger" is in,
> is not in the default PATH environment of command "sh" of Redhat 7.3. It's
> better to use full path name "/usr/share/pcp/bin/pmlogger" instead.

Unfortunately, this will not work if pmlogger has been installed
somewhere else (remember the remote system may not be running
Linux).

This is part of the setup for the pcpqa login that I forgot to mention.

These new words now appear in the README:

        The "pcpqa" user's environment must also be initialized
        so that their shell's path includes all of the PCP binary
        directories, so that all PCP commands are executable without
        full pathnames.  Of most concern would be auxilliary directory
        (usually /usr/pcp/bin or /usr/share/pcp/bin) where commands like
        pmlogger(1), pmhostname(1), mkaf(1), etc.) are installed.

And chk.setup now includes a check for this.



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