@@ -1148,7 +1148,7 @@ int ompi_dpm_spawn(int count, const char *array_of_commands[],
11481148#endif
11491149
11501150 /* check for 'ompi_prefix' (OMPI-specific -- to effect the same
1151- * behavior as --prefix option to orterun )
1151+ * behavior as --prefix option to prun )
11521152 *
11531153 * This is a job-level key
11541154 */
@@ -1472,7 +1472,7 @@ int ompi_dpm_spawn(int count, const char *array_of_commands[],
14721472 }
14731473#endif
14741474
1475- /* see if this is a non-mpi job - if so, then set the flag so ORTE
1475+ /* see if this is a non-mpi job - if so, then set the flag so PRTE
14761476 * knows what to do - job-level key
14771477 */
14781478 ompi_info_get_bool (array_of_info [i ], "ompi_non_mpi" , & non_mpi , & flag );
@@ -2057,7 +2057,7 @@ static int start_dvm(char **hostfiles, char **dash_host)
20572057 will) reset them. If we don't do this, the event
20582058 library may have left some set that, at least on some
20592059 OS's, don't get reset via fork() or exec(). Hence, the
2060- orted could be unkillable (for example). */
2060+ prted could be unkillable (for example). */
20612061 set_handler_default (SIGTERM );
20622062 set_handler_default (SIGINT );
20632063 set_handler_default (SIGHUP );
@@ -2067,9 +2067,9 @@ static int start_dvm(char **hostfiles, char **dash_host)
20672067 /* Unblock all signals, for many of the same reasons that
20682068 we set the default handlers, above. This is noticable
20692069 on Linux where the event library blocks SIGTERM, but we
2070- don't want that blocked by the orted (or, more
2070+ don't want that blocked by the prted (or, more
20712071 specifically, we don't want it to be blocked by the
2072- orted and then inherited by the ORTE processes that it
2072+ prted and then inherited by the PRTE processes that it
20732073 forks, making them unkillable by SIGTERM). */
20742074 sigprocmask (0 , 0 , & sigs );
20752075 sigprocmask (SIG_UNBLOCK , & sigs , 0 );
0 commit comments