Minor wrod wrapping to make the text fit within the show_help lines.

This commit was SVN r23219.

orte/tools/orterun/help-orterun.txt

@@ -269,7 +269,8 @@ Node: %s
 while attempting to start process rank %lu.
 #
 [orterun:proc-failed-to-start]
-%s was unable to start the specified application as it encountered an error:
+%s was unable to start the specified application as it encountered an
+error:
 
 Error name: %s
 Node: %s
@@ -277,7 +278,8 @@ Node: %s
 when attempting to start process rank %lu.
 #
 [orterun:proc-socket-not-avail]
-%s was unable to start the specified application as it encountered an error:
+%s was unable to start the specified application as it encountered an
+error:
 
 Error name: %s
 Node: %s
@@ -285,12 +287,12 @@ Node: %s
 when attempting to start process rank %lu.
 #
 [orterun:proc-failed-to-start-no-status]
-%s was unable to start the specified application as it encountered an error
+%s was unable to start the specified application as it encountered an
-on node %s. More information may be available above.
+error on node %s. More information may be available above.
 #
 [orterun:proc-failed-to-start-no-status-no-node]
-%s was unable to start the specified application as it encountered an error.
+%s was unable to start the specified application as it encountered an
-More information may be available above.
+error.  More information may be available above.
 #
 [debugger requires -np]
 The number of MPI processes to launch was not specified on the command
@@ -402,8 +404,8 @@ a special format used internally by Open MPI for communications. It can
 best be generated by simply directing the ompi-server to put its
 uri in a file, and then giving %s that filename.
 [orterun:multiple-hostfiles]
-Error: More than one hostfile was passed for a single application context, which
+Error: More than one hostfile was passed for a single application
-is not supported at this time.
+context, which is not supported at this time.
 #
 [orterun:conflicting-params]
 %s has detected multiple instances of an MCA param being specified on
@@ -443,13 +445,14 @@ Please remember that the correct format for this command line option is:
 where PID can be either "PID" or "pid".
 #
 [orterun:ompi-server-could-not-get-hnp-list]
-%s was unable to search the list of local %s contact files to find the specified pid.
+%s was unable to search the list of local %s contact files to find the
-You might check to see if your local session directory is available and
+specified pid.  You might check to see if your local session directory
-that you have read permissions on the top of that directory tree.
+is available and that you have read permissions on the top of that
+directory tree.
 #
 [orterun:ompi-server-pid-not-found]
-%s was unable to find an %s with the specified pid of %d that was to be used as the ompi-server.
+%s was unable to find an %s with the specified pid of %d that was to
-The option we were given was:
+be used as the ompi-server.  The option we were given was:
 
 --ompi-server %s
 
@@ -466,7 +469,8 @@ name given was:
 File: %s
 #
 [orterun:multiple-paffinity-schemes]
-Multiple processor affinity schemes were specified (can only specify one):
+Multiple processor affinity schemes were specified (can only specify
+one):
 
 Slot list: %s
 opal_paffinity_alone:  true
@@ -500,7 +504,8 @@ that should be reported to the OMPI developers.
 [orterun:failed-set-paff]
 An attempt to set processor affinity has failed - please check to
 ensure that your system supports such functionality. If so, then
-this is probably something that should be reported to the OMPI developers.
+this is probably something that should be reported to the OMPI
+developers.
 #
 [orterun:topo-not-supported]
 An attempt was made to bind a process to a specific hardware topology
@@ -509,25 +514,25 @@ support such topology-aware actions.  Talk to your local system
 administrator to find out if your system can support topology-aware
 functionality (e.g., Linux Kernels newer than v2.6.18).
 
-Systems that do not support processor topology-aware functionality cannot
+Systems that do not support processor topology-aware functionality
-use "bind to socket" and other related functionality.
+cannot use "bind to socket" and other related functionality.
 
   Local host:        %s
   Action attempted:  %s %s
   Application name:  %s
 #
 [orterun:binding-not-avail]
-A request to bind the processes if the operating system supports
+A request to bind the processes if the operating system supports such
-such an operation was made, but the OS does not support this operation:
+an operation was made, but the OS does not support this operation:
 
   Local host:        %s
   Action requested:  %s
   Application name:  %s
 
 Because the request was made on an "if-available" basis, the job was
-launched without taking the requested action. If this is not the desired
+launched without taking the requested action. If this is not the
-behavior, talk to your local system administrator to find out if your
+desired behavior, talk to your local system administrator to find out
-system can support the requested action.
+if your system can support the requested action.
 #
 [orterun:not-enough-resources]
 Not enough %s were found on the local host to meet the requested
@@ -557,12 +562,6 @@ resources:
 
 Please check your boundaries and try again.
 #
-[orterun:affinity-not-supported]
-A request was made to bind processes, but process affinity is
-not supported on this node:
-
-  Local host: %s
-#
 [orterun:proc-comm-failed]
 A critical communication path was lost to:
 
@@ -588,7 +587,8 @@ no further info is available.
 the job to be terminated.
 #
 [orterun:proc-heartbeat-failed]
-%s failed to receive scheduled heartbeat communications from a remote process:
+%s failed to receive scheduled heartbeat communications from a remote
+process:
 
   Process name: %s
   Node:         %s