Ctrl-C in shell kills associated server processes on *nix
Description
It's been reported by Mac users that hitting Ctrl-C in the shell for any reason will kill any associated server processes that were started by the CLI. This may be related to the Thread.interrupt() call.
Gliffy Diagrams
Activity
Show:
Brad Wood April 2, 2018 at 4:32 AM
There is a shell script that will be used automatically on non-Windows OS's that will run background server starts through nohup and redirect the output to a file which will be tailed so flags like --debug can still stream the console output while the server is coming up. The nohup command will ensure that the server runs in a separate process group from the CLI so interrupt signals from the shell will not be propagated to any servers. --console starts will not use nohup, but they don't need to since they purposefully run in the foreground and are stopped by Ctrl-C.
It's been reported by Mac users that hitting Ctrl-C in the shell for any reason will kill any associated server processes that were started by the CLI. This may be related to the Thread.interrupt() call.