--- Begin Message ---
|
Subject: |
openmpi changes |
|
Date: |
Mon, 24 Jul 2017 19:34:56 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
I assume the only one of these that's questionable is the SGE one. It
used to be the default, and I don't know of any way it could be
problematic -- the support just looks at the environment to determine
whether to use qrsh for remote startup. Debian and Fedora both enable
it.
0001-mpi.scm-gnu-openmpi-Update-to-1.10.7.patch
Description: Version update
0002-mpi.scm-gnu-openmpi-Enable-SGE-support.patch
Description: enable SGE
0004-mpi.scm-gnu-openmpi-It-s-MPI-3.0-not-MPI-2.patch
Description: fix description
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: [bug#27806] openmpi changes |
|
Date: |
Wed, 26 Jul 2017 22:38:12 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Dave Love <address@hidden> skribis:
> Ludovic Courtès <address@hidden> writes:
>
>> Hi Dave,
>>
>> I adjusted the commit log and applied the first two patches.
>>
>> Dave Love <address@hidden> skribis:
>>
>>> I assume the only one of these that's questionable is the SGE one. It
>>> used to be the default, and I don't know of any way it could be
>>> problematic -- the support just looks at the environment to determine
>>> whether to use qrsh for remote startup. Debian and Fedora both enable
>>> it.
>>
>> To be clear: if there’s no environment variable suggesting that SGE is
>> being used, then it won’t try to use qrsh, right?
>
> Yes, and that flag is long-established in other distributions which add
> more intrusive support for resource managers.
Sounds good, applied.
Thank you!
Ludo’.
--- End Message ---