Roger Pack
Roger Pack
Perhaps you could find the offending commit in crystal-pg?
https://github.com/jruby/jruby/blob/c3385b8feac7c05675a5f430b0d9b79f0edc5d37/core/src/main/java/org/jruby/RubyProcess.java#L1286 is how jruby does it, well for 0 and 9 anyway. > 0 liveness > 1 HUP (hang up) > 2 INT (interrupt) > 3 QUIT (quit) > 6...
My hunch is they always send ctrl+break so that it works for "both pids and process groups" in case they happen to be targeting a process group? Kind of weird......
@sancarn I think one of the "cons" is that after running code like that you would no longer be bound to your initial console (as in...printf would now go no...
Unrelated to the standard linux signals, I wonder if there's a way to add handlers for other windows signals, like CTRL_LOGOFF_EVENT https://docs.microsoft.com/en-us/windows/console/handlerroutine or maybe it's already possible dunno. Might be...
It's not much work/overhead, and makes it so you don't have to remember/use a "different way to kill process based on the current OS" as it were...I like maltevoos' roadmap...
See #156 as well
For followers, it appears this might be related to not having virtualization support at the CPU level: https://github.com/minishift/minishift/issues/2385#issuecomment-392457775 (ex: old macbook)
Update: appears this behavior only occurs if the connection you are currently modifying is named `**new**`
Out of scope, might be nice to move the faq into the codebase so it's more easily modifiable :) Ref: https://github.com/ivmai/bdwgc/blob/master/doc/overview.md