This file is indexed.

/usr/share/openmpi/help-plm-tm.txt is in openmpi-common 1.6.5-8.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
# -*- text -*-
#
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
#                         University Research and Technology
#                         Corporation.  All rights reserved.
# Copyright (c) 2004-2005 The University of Tennessee and The University
#                         of Tennessee Research Foundation.  All rights
#                         reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart, 
#                         University of Stuttgart.  All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
#                         All rights reserved.
# $COPYRIGHT$
# 
# Additional copyrights may follow
# 
# $HEADER$
#
[tm-bad-launchid]
The TM (PBS / Torque) process starter cannot spawn the specified
application on a remote node due to an invalid launch_id.

This is most likely due to use of the "--hostfile" option to the
command line with one or more hosts in that file not having
been allocated to this job.

Removing "--hostfile" from the command line will likely allow the
application to be launched.
#
[multiple-prefixes]
Multiple different --prefix options were specified to mpirun for the
same node.  This is a fatal error for the TM (PBS / Torque) process
starter in Open MPI.

The first two prefix values supplied for node %s were:
    %s
and %s
#
[tm-spawn-failed]
The TM (PBS / Torque) process starter failed to spawn a daemon (orted)
on a remote node.

Command line: %s
Node name: %s
Launch id: %d

If you do not understand this error mesage, please try the following:

1. Ensure that the executable "orted" is in your PATH
2. Use the --prefix option to indicate where we can
   find that executable
3. Talk to your local system administrator
#
[no-local-slave-support]
A call was made to launch a local slave process, but no support
is available for doing so. Launching a local slave requires support
for either rsh or ssh on the backend nodes where MPI processes
are running.

Please consult with your system administrator about obtaining
such support.