Wyatt,
It depends on how the remote system handles non-interative non-login shells. For bash and other "normal" shells, the user can usually set the environment using .bashrc or something similar. For ksh, it is practically impossible to do anything.
In any case, it's an issue with the target system, there's not really anything that can be done from the local side, other than manually configuring environment variables.
Regards, Greg
On May 31, 2012, at 7:32 PM, Wyatt Spear wrote: Greetings,
The ETFW relies on the user having set up their environment on the remote system to make certain tools available. In the latest from Head only the most minimal possible environment populates this execution mode. Running env through an IRemoteProcess builder returns this anemic set:
SSH_CLIENT=127.0.0.1 52127 22 USER=wspear SHLVL=1 HOME=/home/wspear OLDPWD=/home/wspear XDG_SESSION_COOKIE=9c9c2e1a622e131a08e489150000000d-1338505599.135007-876977824
LOGNAME=wspear _=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash PWD=/home/wspear SSH_CONNECTION=127.0.0.1 52127 127.0.0.1 22
Is there any way to launch on a remote system with the full environment defined by bash?
Thanks, Wyatt
_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-dev
|