Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Disable SIGUSR1 on JRuby #425

Closed
denisdefreyne opened this issue Apr 22, 2014 · 2 comments
Closed

Disable SIGUSR1 on JRuby #425

denisdefreyne opened this issue Apr 22, 2014 · 2 comments
Labels
type:enhancement ✨

Comments

@denisdefreyne
Copy link
Member

nanoc uses SIGUSR1 to print debugging information. This does not work on JRuby, however, and even causes a warning:

The signal USR1 is in use by the JVM and will not work correctly on this platform

I see two options:

  • Using another signal on JRuby (SIGUSR2? SIGHUP?)
  • Disabling printing debug information on JRuby and silencing the warnings
@denisdefreyne denisdefreyne changed the title Disable USR1 on JRuby Apr 22, 2014
@denisdefreyne denisdefreyne mentioned this issue Apr 23, 2014
Merged
@gpakosz
Copy link
Member

gpakosz commented Apr 29, 2014

According to http://www.oracle.com/technetwork/java/javase/signals-139944.html SIGUSR2 is bound to the same kind of restrictions as SIGUSR1.

What about trapping SIGABRT: dump debug information then abort since the only use case this feature seems to cover is: nanoc hangs and I want to get a stack trace to understand where it's stuck.
@denisdefreyne
Copy link
Member Author

Fixed by PR #426.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement ✨
2 participants
@denisdefreyne @gpakosz