p4_error: Child process exited while making connection to remote process
14, Mar 2013 19:16
If this fails, then you may need a ‘.rhosts’ or ‘/etc/hosts.equiv’ file (you may need
to see your system administrator) or you may need to use the p4 server. Another possible
problem is the choice of the remote shell program; some systems have several. Check with
your systems administrator about which version of rsh or remsh you should be using.
If your system allows a ‘.rhosts’ file, do the following:
• Create a file .rhosts in your home directory
• Change the protection on it to user read/write only: chmod og-rwx .rhosts.
• Add one line to the .rhosts file for each processor that you want to use. The format is
For example, if your username is doe and you want to user machines a.our.org and
b.our.org, your .rhosts file should contain
Note the use of fully qualified host names (some systems require this).
On networks where the use of .rhosts files is not allowed, (such as the one in MCS at
Argonne), you should use the p4 server to run on machines that are not trusted by the
machine that you are initiating the job from.
Finally, you may need to use a non-standard rsh command within MPICH. MPICH must be
reconfigured with -rsh=command name, and perhaps also with -rshnol if the remote shell
command does not support the -l argument. Systems using Kerberos and/or AFS may