Home
last modified time | relevance | path

Searched hist:2183 (Results 1 – 2 of 2) sorted by relevance

/unit/src/ruby/
H A Dnxt_ruby.cdiff 2183:5f7bba4cc968 Tue Aug 30 23:49:00 UTC 2022 Andrew Clayton <a.clayton@f5.com> Ruby: prevented a segfault on receiving SIGINT (^C).

As was reported[0] by @travisbell on GitHub, if running unit from the
terminal in the foreground when hitting ^C to exit it, the ruby
application processes would segfault if they were using threads.

It's not 100% clear where the actual problem lies, but it _looks_ like
it may be in ruby.

The simplest way to deal with this for now is to just ignore SIGINT in
the ruby application processes. Unit will still receive and handle it,
cleanly shutting everything down.

For people who want to handle SIGINT in their ruby application running
under unit they can still trap SIGINT and it will override the ignore.

[0]: https://github.com/nginx/unit/issues/562#issuecomment-1223229585

Closes: https://github.com/nginx/unit/issues/562
/unit/docs/
H A Dchanges.xmldiff 2183:5f7bba4cc968 Tue Aug 30 23:49:00 UTC 2022 Andrew Clayton <a.clayton@f5.com> Ruby: prevented a segfault on receiving SIGINT (^C).

As was reported[0] by @travisbell on GitHub, if running unit from the
terminal in the foreground when hitting ^C to exit it, the ruby
application processes would segfault if they were using threads.

It's not 100% clear where the actual problem lies, but it _looks_ like
it may be in ruby.

The simplest way to deal with this for now is to just ignore SIGINT in
the ruby application processes. Unit will still receive and handle it,
cleanly shutting everything down.

For people who want to handle SIGINT in their ruby application running
under unit they can still trap SIGINT and it will override the ignore.

[0]: https://github.com/nginx/unit/issues/562#issuecomment-1223229585

Closes: https://github.com/nginx/unit/issues/562