MSP-Greg

See https://github.com/eventmachine/eventmachine/pull/970 Windows Ruby 3.1 & 3.2 are using OpenSSL 3, also newer Rubies on Ubuntu 22.04

Yes. [eventmachine-1.2.7-x64-mingw32](https://rubygems.org/gems/eventmachine/versions/1.2.7-x64-mingw32) was not properly built. It only contains *.so files for Ruby 2.0 thru 2.3, and the gem has no `required_ruby_version` constraints. So, RubyGems thinks it's a valid gem...

@sj26 Ok, I've got a [branch](https://github.com/sj26/mailcatcher/compare/main...MSP-Greg:mailcatcher:00-em-gemfile) with four commits. It compiles on all OS's. It adds EventMachine from https://github.com/eventmachine/eventmachine/pull/970 to the Gemfile, as below: ```ruby gem 'eventmachine', github: 'https://github.com/eventmachine/eventmachine/pull/970' ```...

Made changes in another branch, got it to start the CI, then hit: ``` D:/a/mailcatcher/mailcatcher/lib/mail_catcher.rb:193:in `trap': unsupported signal `SIGQUIT' (ArgumentError) trap(signal) { EM.add_timer(0) { quit! } } ^^^^^^ from D:/a/mailcatcher/mailcatcher/lib/mail_catcher.rb:193:in...

The other branch is [00-windows](https://github.com/sj26/mailcatcher/compare/main...MSP-Greg:mailcatcher:00-windows) in my fork. Made a few changes, the CI run is [here](https://github.com/MSP-Greg/mailcatcher/actions/runs/5707706544). Notice the log [here](https://github.com/MSP-Greg/mailcatcher/actions/runs/5707706544/job/15464647611#step:7:128), which shows several messages `Terminate batch job (Y/N)? `....

@Apteryks I haven't had the time, but we/I will have PR's for this, probably this weekend.

@skliew See PR #3338, I believe it fixes this issue. Thanks for reporting it.

Thanks for workingon the repo example. I've got a test verifying this behavior. A quick look at possible fixes showed that 'no signalling to systemd at all' might be messy,...

@slondr I think more data might be helpful. I set fork_worker to 1000, and threw a wrk stream at a server, and it did restart, so I'm not sure what...

@slondr Most of my local test code is for master; I probably should have checked 5.6.5 or 5.6.4. I'll check a release sometime soon...