pcp
[Top] [All Lists]

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

To: kenmcd@xxxxxxxxxxxxxxxxx
Subject: RE: I find the cause of the failure in case 374
From: "Zhang, Sonic" <sonic.zhang@xxxxxxxxx>
Date: Thu, 16 Jan 2003 09:25:12 +0800
Cc: "PCP (E-mail)" <pcp@xxxxxxxxxxx>
Sender: pcp-bounce@xxxxxxxxxxx
Hi kenmcd,

        I am afraid that your suggestion can't work on Red Hat 7.3.
        The default shell is bash. I have already added the required path
string to file ".bash_profile" in the pcpqa's home directory on the remote
host. But it doesn't work for "rsh remote -l pcpqa sh". It seems the bash
shell doesn't support this function when run it via "rsh".

        That why I have to create a symbolic link in folder /bin/ .

        Sonic Zhang


-----Original Message-----
From: kenmcd@xxxxxxxxxxxxxxxxx [mailto:kenmcd@xxxxxxxxxxxxxxxxx]
Sent: 2003?1?16? 4:29
To: Zhang, Sonic
Cc: PCP (E-mail)
Subject: RE: I find the cause of the failure in case 374


On Mon, 13 Jan 2003, Zhang, Sonic wrote:

> Hi,
> 
>       The current problem is that command "sh" in "rsh remotehost -l pcpqa
> sh" doesn't use any environment config file of user pcpqa. So, I fail to
set
> the full path of pmlogger for "sh". Its default path variable is
> "/bin:/usr/bin". The only way that I know is create a symbolic link of
> pmlogger in folder /bin .
> 
>       Do you have any good idea?

Edit the .profile or .cshrc or .whatever for the "pcpqa" user on all
of the remote systems to add all of the required PCP directories to the
user's $PATH.

You need to fix this in the setup of the "pcpqa" login on the QA machines,
_not_ in the PCP QA scripts.

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