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.

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

Disable SIGUSR1 on JRuby #425

Closed
ddfreyne opened this Issue Apr 22, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@ddfreyne
Member

ddfreyne commented Apr 22, 2014

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

@ddfreyne ddfreyne changed the title from Disable USR1 on JRuby to Disable SIGUSR1 on JRuby Apr 22, 2014

@gpakosz

This comment has been minimized.

Show comment
Hide comment
@gpakosz

gpakosz Apr 29, 2014

Member

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.

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.

@ddfreyne

This comment has been minimized.

Show comment
Hide comment
@ddfreyne

ddfreyne May 1, 2014

Member

Fixed by PR #426.

Member

ddfreyne commented May 1, 2014

Fixed by PR #426.

@ddfreyne ddfreyne closed this May 1, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment