You copied the Doc URL to your clipboard.

7 Configuration

Arm Performance Reports generally requires no configuration before use.

If you only intend to use Arm Performance Reports and have checked that it works on your system without extra setup then you can safely ignore the rest of this section.

7.1 Compute node access

When Arm Performance Reports needs to access another machine as part of starting one of MPICH 1-3, Intel MPI, and SGI MPT, it attempts to use the secure shell, ssh, by default.

However, this may not always be appropriate, ssh may be disabled or be running on a different port to the normal port 22. In this case, you can create a file called remote-exec which is placed in your ~/.allinea directory and Arm Performance Reports will use this instead.

Arm Performance Reports checks for the script at ~/.allinea/remote-exec, and it will be executed as follows:


   remote-exec HOSTNAME APPNAME [ARG1] [ARG2] ...

The script should start APPNAME on HOSTNAME with the arguments ARG1 ARG2 without further input (no password prompts). Standard output from APPNAME will appear on the standard output of remote-exec.

SSH based remote-exec

A remote-exec script using ssh running on a non-standard port could look as follows:


   #!/bin/sh 
ssh -P {port-number} $*

In order for this to work without prompting for a password, you should generate a public and private SSH key, and ensure that the public key has been added to the ~/.ssh/authorized_keys file on machines you wish to use.

See the ssh-keygen manual page for more information.

Testing

Once you have set up your remote-exec script, it is recommended that you test it from the command line. For example:


   ~/.allinea/remote-exec TESTHOST uname -n

This returns the output of uname -n on TESTHOST, without prompting for a password.

If you are having trouble setting up remote-exec, please contact Arm support at Arm support for assistance.

Windows

The functionality described above is also provided by the Windows remote client. There are two differences:

  • The script is named remote-exec.cmd rather than remote-exec.
  • The default implementation uses the plink.exe executable supplied with Arm Performance Reports.
Was this page helpful? Yes No