Many stacks have ON_CHANGE commands that end the process by themselves and there is no need to kill them.
Currently the controller tries to kill them in this case, and prints out warning messages which say the kill failed and there is no such process
Outcome desired:
Either:
suppress the above messages
or
*2. Use a similar technique that we use to determine server failures and restarts in the on change events where we send a benign signal to determine if the process is alive.
Then we could avoid unnecessary kill actions.
Many stacks have ON_CHANGE commands that end the process by themselves and there is no need to kill them.
Currently the controller tries to kill them in this case, and prints out warning messages which say the kill failed and there is no such process
Outcome desired: Either:
or
*2. Use a similar technique that we use to determine server failures and restarts in the on change events where we send a benign signal to determine if the process is alive. Then we could avoid unnecessary kill actions.