Child processes are no longer terminated after upgrade forever v0.10.2 -> v0.14.1

[srlowe]

We have a node script that spawns a number of child processes using child_process.fork(). We were using forever to manage this parent script, and issuing a forever restart would kill the process and the children before restarting everything. Since we upgraded to forever 0.14.1 the child processes are no longer killed, but rather are left running, resulting in duplicated processes running on the server after a forever restart.

Could anyone shed any light on this behaviour change?

Thank you.

Additional Info:

I've tried --killSignal=SIGTERM (this seems to be a new option), but it doesn't change the behaviour.

[srlowe]

Looks like it might be related to this issue (which doesn't seem to have received much attention) #420

[neebz]

it doesn't occur when I run forever(0.14.1) on Yosemite.

however my child processes are not killed when I use forever on Amazon EC2 instances.

[przemyslawpluta]

Same issue here.

[resteinbock]

same here

[indexzero]

Can you try with forever@0.15.2 and try again?

[Agamnentzar]

This is still an issue in forever@0.15.3