From 8c1f420bd7d8530529e3fe1b55cd0bb73736da9b Mon Sep 17 00:00:00 2001 From: Howard Pritchard Date: Tue, 16 Dec 2025 11:22:49 -0700 Subject: [PATCH] docs: update gridengine to use prte mca param replace orte_forward_job_control with ess_base_forward_signals remove error contact Ralph message Signed-off-by: Howard Pritchard --- docs/launching-apps/gridengine.rst | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/docs/launching-apps/gridengine.rst b/docs/launching-apps/gridengine.rst index 462cb26b61e..1e8a6c59dfc 100644 --- a/docs/launching-apps/gridengine.rst +++ b/docs/launching-apps/gridengine.rst @@ -177,9 +177,7 @@ like this batch script can be used: #$ -pe ompi 16 #$ -j y #$ -l h_rt=00:20:00 - mpirun -n 16 -mca orte_forward_job_control 1 mpi-hello-world - -.. error:: Ralph: Does ``orte_forward_job_control`` still exist? + mpirun -n 16 --prtemca ess_base_forward_signals mpi-hello-world However, one has to make one of two changes to this script for things to work properly. By default, a SIGUSR1 signal will kill a shell @@ -196,7 +194,7 @@ to handle it: #$ -pe ompi 16 #$ -j y #$ -l h_rt=00:20:00 - exec mpirun -n 16 -mca orte_forward_job_control 1 mpi-hello-world + exec mpirun -n 16 --prtemca ess_base_forward_signals mpi-hello-world Alternatively, one can catch the signals in the script instead of doing an exec on the mpirun: @@ -225,7 +223,7 @@ an exec on the mpirun: trap sigusr1handler SIGUSR1 trap sigusr2handler SIGUSR2 - mpirun -n 16 -mca orte_forward_job_control 1 mpi-hello-world + mpirun -n 16 --prtemca ess_base_forward_signals mpi-hello-world Grid Engine job suspend / resume support ---------------------------------------- @@ -238,14 +236,12 @@ the ``mpi-hello-world``. By default, this feature is not enabled. This means that both the SIGTSTP and SIGCONT signals will simply be consumed by the ``mpirun`` -process. To have them forwarded, you have to run the job with ``--mca -orte_forward_job_control 1``. Here is an example on Solaris: - -.. error:: TODO Ralph: does ``orte_forward_job_control`` still exist? +process. To have them forwarded, you have to run the job with ``--prtemca +ess_base_forward_signals``. Here is an example using Solaris: .. code-block:: sh - shell$ mpirun -mca orte_forward_job_control 1 -n 2 mpi-hello-world + shell$ mpirun --prtemca ess_base_forward_signals -n 2 mpi-hello-world In another window, we suspend and continue the job: