| /unit/pkg/rpm/ |
| H A D | Makefile.php | diff 562:406b163dad62 Thu Mar 01 20:03:00 UTC 2018 Andrei Belov <defan@nginx.com> Packages: added openSUSE Leap, openSUSE Tumbleweed, SLES support.
|
| H A D | Makefile.perl | diff 562:406b163dad62 Thu Mar 01 20:03:00 UTC 2018 Andrei Belov <defan@nginx.com> Packages: added openSUSE Leap, openSUSE Tumbleweed, SLES support.
|
| H A D | Makefile.python36 | diff 562:406b163dad62 Thu Mar 01 20:03:00 UTC 2018 Andrei Belov <defan@nginx.com> Packages: added openSUSE Leap, openSUSE Tumbleweed, SLES support.
|
| H A D | Makefile.python27 | diff 562:406b163dad62 Thu Mar 01 20:03:00 UTC 2018 Andrei Belov <defan@nginx.com> Packages: added openSUSE Leap, openSUSE Tumbleweed, SLES support.
|
| H A D | Makefile.go | diff 562:406b163dad62 Thu Mar 01 20:03:00 UTC 2018 Andrei Belov <defan@nginx.com> Packages: added openSUSE Leap, openSUSE Tumbleweed, SLES support.
|
| H A D | unit.spec.in | diff 562:406b163dad62 Thu Mar 01 20:03:00 UTC 2018 Andrei Belov <defan@nginx.com> Packages: added openSUSE Leap, openSUSE Tumbleweed, SLES support.
|
| H A D | Makefile | diff 562:406b163dad62 Thu Mar 01 20:03:00 UTC 2018 Andrei Belov <defan@nginx.com> Packages: added openSUSE Leap, openSUSE Tumbleweed, SLES support.
|
| /unit/src/ruby/ |
| H A D | nxt_ruby.c | diff 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
diff 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
diff 2164:52fbf5e84a42 Thu Jul 28 03:00:00 UTC 2022 Zhidao HONG <z.hong@f5.com> Ruby: fixed segfault on SIGTERM signal.
This closes #562 issue on GitHub.
|
| /unit/docs/ |
| H A D | changes.xml | diff 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
diff 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
diff 2164:52fbf5e84a42 Thu Jul 28 03:00:00 UTC 2022 Zhidao HONG <z.hong@f5.com> Ruby: fixed segfault on SIGTERM signal.
This closes #562 issue on GitHub.
|