You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When havoc kills logger, heart or url_prim_loader it kills the entire node. Is this a feature or a bug? Or could it be that some internals of OTP has changed in such a way that havoc now tries to kill those processes?
I see that that havoc specifically checks to not kill application_controller, but there can be other processes linked to init too.
Would it be an idea to specifically check if a proces is linked to init? Or maybe introduce a configurable do_not_kill list with names of processes which should not be killed.
The text was updated successfully, but these errors were encountered:
It is possible logger, heart and url_prim_loader were added to OTP after I wrote this initial implementation. It should be easy enough to add them to the OTP_APPS definition that is currently used in order to not kill them by default.
There is already the killable_callback attribute that you can pass in the configuration in order to let you decide whether or not a given process should be killed. With that said, it is worth exploring whether other process should not be killed by default other than just the application_controller.
When havoc kills
logger
,heart
orurl_prim_loader
it kills the entire node. Is this a feature or a bug? Or could it be that some internals of OTP has changed in such a way that havoc now tries to kill those processes?I see that that havoc specifically checks to not kill
application_controller
, but there can be other processes linked toinit
too.Would it be an idea to specifically check if a proces is linked to
init
? Or maybe introduce a configurable do_not_kill list with names of processes which should not be killed.The text was updated successfully, but these errors were encountered: