FAQ

Set FQDN if hostname of the client host cannot be accessed.

In the OmniRPC system, after the agent's invocation, the program on the remote host requests access to the client host. Therefore, it is necessary for the remote host to know the hostname which can be accessed to the client host By default, the OmniRPC system uses the hostname through hostname commands. But, in some settings, there may exits a hostname which cannot be accessed from an outside network exists. You should set FQDN(Full Qualified Domain Name) by the hostname command or environment variable OMRPC_HOSTNAME as FDQN.

(csh or tcsh)
% setenv OMRP_HOSTNAME  FQDN  
or
(bash)
$ export OMRP_HOSTNAME  FQDN 

There is the same problem in the Globus Toolkit environment. In this case, set the environmental variable GLOBUS_HOSTNAME to FQDN. for more details, please see Globus information.

Use SSH to invoke the remote executable program at cluster nodes.

Usually cluster nodes accept RSH, So, the agent can invoke the remote executable program on the cluster nodes. But in some situations, the cluster nodes restrict the use of RSH and support SSH. Therefore, you can use SSH to invoke remote executable programs. You should write explicitly to use SSH. You can change the cluster nodes file (which is introduced in Use of a built-in round-robiin scheduler) as below.

hpc1 ssh
hpc2 ssh
hpc3 ssh

If ssh is omitted in the above description, rsh is used.