[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Proposed change to Remote Tools
|
This has been a problem for the ETFW which needs access to the remote PATH variable to locate tools. I'm in favor of this fix.
=Wyatt
On Mon, Oct 29, 2012 at 3:45 PM, Greg Watson
<g.watson@xxxxxxxxxxxx> wrote:
Currently, there is a problem (bug 393106) with system monitoring if the monitoring commands are in a non standard location. This is because remote processes started with Remote Tools use the command "/bin/sh -c <cmd_to_launch>" on the remote machine. This starts a non-login, non-interactive shell that does not read the user's .profile script, so there is no opportunity to modify the environment, set the path, etc.
The simplest solution to this is to change the remote command to be "/bin/bash -l -c <cmd_to_launch>". This will cause bash to be started up as a login shell, so it will read the user's .profile correctly. I'd like to propose making this change for PTP 6.0.x. Most systems that we support have bash available, so I don't think this should be an issue. The only disadvantage is that if the user has something really weird in their .profile, it could cause problems.
A longer term solution is to allow the target system configuration file to be used to specify the correct location of these commands, but this will only be available in the Kepler time frame.
If anyone has any comments on this, please let me know.
Greg
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
