Protect against the envar version of the Slurm custom args param #2031
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@abouteiller @naughtont3 See what you think of this approach to the problem. It worked for me in my Docker containers. |
|
True - but if we don’t find “srun”, then we cannot launch anyway, so I think we are okay as-is.
… On Oct 7, 2024, at 2:10 PM, Aurelien Bouteiller ***@***.***> wrote:
I remember it was possible to install only slurmd on the compute images (that is, not having slurm as a command), maybe using slurmd --version is safer.
—
Reply to this email directly, view it on GitHub <#2031 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAST5YDJS4LXSRHYUUUKY73Z2LTCZAVCNFSM6AAAAABPN3HXS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJXG44TQMBRGA>.
You are receiving this because you authored the thread.
|
|
Yes I removed the comment already :)
Best,
Aurelien
… On Oct 7, 2024, at 16:31, Ralph Castain ***@***.***> wrote:
True - but if we don’t find “srun”, then we cannot launch anyway, so I think we are okay as-is.
> On Oct 7, 2024, at 2:10 PM, Aurelien Bouteiller ***@***.***> wrote:
>
>
> I remember it was possible to install only slurmd on the compute images (that is, not having slurm as a command), maybe using slurmd --version is safer.
>
> —
> Reply to this email directly, view it on GitHub <#2031 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAST5YDJS4LXSRHYUUUKY73Z2LTCZAVCNFSM6AAAAABPN3HXS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJXG44TQMBRGA>.
> You are receiving this because you authored the thread.
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
abouteiller
reviewed
Oct 7, 2024
Protect against the envar version of the Slurm custom args MCA param. This is an unfortunate hack that hopefully will eventually go away. See both of the following for detailed explanations and discussion: openpmix#1974 open-mpi/ompi#12471 Orgs/users wanting to add custom args to the internal "srun" command used to spawn the PRRTE daemons must do so via the default MCA param files (system or user), or via the prterun (or its proxy) cmd line Signed-off-by: Ralph Castain <[email protected]>
This was referenced Oct 14, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Protect against the envar version of the Slurm
custom args MCA param. This is an unfortunate
hack that hopefully will eventually go away.
See both of the following for detailed
explanations and discussion:
#1974
open-mpi/ompi#12471
Orgs/users wanting to add custom args to the
internal "srun" command used to spawn the
PRRTE daemons must do so via the default MCA
param files (system or user), or via the
prterun (or its proxy) cmd line