The plugin now stops and starts the notify watch process(es) on the host when running vagrant provision. I'm implementing this because a SIGINT sent to a running vagrant process kills its children (even if they are detached). Then when running vagrant provision, the stopped process(es) do not start up again.
This change helps keep a constant and predictable state of the processes in defense of any SIGINTs sent to the main vagrant process.
The plugin now stops and starts the notify watch process(es) on the host when running
vagrant provision
. I'm implementing this because a SIGINT sent to a running vagrant process kills its children (even if they are detached). Then when runningvagrant provision
, the stopped process(es) do not start up again.This change helps keep a constant and predictable state of the processes in defense of any SIGINTs sent to the main vagrant process.
This contains changes found in https://github.com/mhallin/vagrant-notify-forwarder/pull/1 as well. Once https://github.com/mhallin/vagrant-notify-forwarder/pull/1 is merged, this PR should contain fewer changes.