Hi, > Am 01.08.2017 um 18:36 schrieb Dave Love <dave.l...@manchester.ac.uk>: > > Gilles Gouaillardet <gil...@rist.or.jp> writes: > >> Dave, >> >> >> unless you are doing direct launch (for example, use 'srun' instead of >> 'mpirun' under SLURM), >> >> this is the way Open MPI is working : mpirun will use whatever the >> resource manager provides >> >> in order to spawn the remote orted (tm with PBS, qrsh with SGE, srun >> with SLURM, ...). >> >> >> then mpirun/orted will fork&exec the MPI tasks. > > I know quite well how SGE works with openmpi, which isn't special -- > I've done enough work on it. SGE tracks the process tree under orted > just like under bash, even if things daemonize. The OP was correct. > > I should qualify that by noting that ENABLE_ADDGRP_KILL has apparently > never propagated through remote startup,
Isn't it a setting inside SGE which the sge_execd is aware of? I never exported any environment variable for this purpose. -- Reuti > so killing those orphans after > VASP crashes may fail, though resource reporting works. (I never > installed a fix for want of a test system, but it's not needed with > Linux cpusets.) > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
