Dear Torsten,
Unless you specify differently, processes on remote hosts are created by
'rsh' (which should alias to ssh), while processes on the local host are
create by a non-interactive 'bash' shell. By default, non-interactive
bash shells do not run your ~/.bashrc script. This is possibly why
creating local processes for parallel search complain about "ozengine:
not found". In order to make non-interactive bash shells run the init
script, the environment variable BASH_ENV should be set to the file name
of the init script.
Check whether the following works or not (it should not):
% bash ozengine
Then check the following:
% export BASH_ENV=~/.bashrc
% bash ozengine
If you setup the PATH in the ~/.bashrc file, the latter command should
work. The 'export' command should be done once per interactive shell.
Maybe you don't want to run the whole ~/.bashrc file. In that case,
make a separate script, and modify BASH_ENV accordingly.
I hope these tricks will help.
Cheers,
raph
Torsten Anders wrote:
Dear Raphael,
thanks for your reply. Actually, on the remote machine the
~/.bash_profile file already did add the Mozart bin directory to PATH.
My home dir is shared by all cluster nodes, and so are all ~/.* files.
When I log into the remote machine by ssh then ozengine is found all
right. However, parallel search does not work via ssh, instead I get the
following error (in the emulator on the localhost)
bash: line 0: exec: ozengine: not found
What are likely causes for this problem besides some wrongly set PATH?
In order to confirm that PATH is really the problem here, how can I
display what the value of PATH is
for the remote ozengine call?
Thank you very much!
Best
Torsten
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
