Skip to content

Conversation

@hjelmn
Copy link
Member

@hjelmn hjelmn commented Jan 12, 2017

  • ess/hnp: add support for forwarding additional signals

This commit adds support to the hnp ess module to forward additional
signals beyond the default SIGUSR1, SIGUSR2, SIGSTP, and SIGCONT.

Signed-off-by: Nathan Hjelm hjelmn@lanl.gov

  • Generalize this a bit to allow a broader range of signals to be forwarded. Turns out that SIGURG is now a "standard" signal, though the value differs across systems. So setup to forward it (and some friends) if they are defined. Allow users to provide the signal name (instead of the integer value) as the value of even the more common signals does vary across systems. Don't limit the number that can be supported.

Signed-off-by: Ralph Castain rhc@open-mpi.org

  • ess/hnp: fix some bugs in the signal forwarding code

This commit fixes two bugs:

  • signals_set needs to be set even if no signals are being
    forwarded. If it is not set we will SEGV in libevent if
    ess_hnp_forward_signals == none.

  • SIGTERM and SIGHUP are handled with a different type of handler. Do
    not allow the user to specify these to be forwarded.

Signed-off-by: Nathan Hjelm hjelmn@lanl.gov

  • We are sure to get "dinged" if error messages aren't nicely output via show_help, so do so here

Signed-off-by: Ralph Castain rhc@open-mpi.org

(cherry picked from commit 110840f)
Signed-off-by: Nathan Hjelm hjelmn@lanl.gov

@hjelmn hjelmn added the bug label Jan 12, 2017
@hjelmn hjelmn added this to the v2.1.0 milestone Jan 12, 2017
@hjelmn hjelmn requested a review from rhc54 January 12, 2017 17:17
* ess/hnp: add support for forwarding additional signals

This commit adds support to the hnp ess module to forward additional
signals beyond the default SIGUSR1, SIGUSR2, SIGSTP, and SIGCONT.

Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>

* Generalize this a bit to allow a broader range of signals to be forwarded. Turns out that SIGURG is now a "standard" signal, though the value differs across systems. So setup to forward it (and some friends) if they are defined. Allow users to provide the signal name (instead of the integer value) as the value of even the more common signals does vary across systems. Don't limit the number that can be supported.

Signed-off-by: Ralph Castain <rhc@open-mpi.org>

* ess/hnp: fix some bugs in the signal forwarding code

This commit fixes two bugs:

 - signals_set needs to be set even if no signals are being
   forwarded. If it is not set we will SEGV in libevent if
   ess_hnp_forward_signals == none.

 - SIGTERM and SIGHUP are handled with a different type of handler. Do
   not allow the user to specify these to be forwarded.

Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>

* We are sure to get "dinged" if error messages aren't nicely output via show_help, so do so here

Signed-off-by: Ralph Castain <rhc@open-mpi.org>

(cherry picked from commit 110840f)
Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>
@hppritcha
Copy link
Member

bot:mellanox:retest

@hppritcha
Copy link
Member

@jsquyres ready to go.

@jsquyres jsquyres merged commit b3da29a into open-mpi:v2.x Jan 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants