fix: send sighup after installing when synchronizer boots, remove load com… #324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Temporary fix to address the problem reported by Patina in which plugins fail to run reliably after a home-app deploy.
The failure mode is a race condition in which plugins may be loaded into memory before the synchronizer has finished installing them on the file system. This solution causes the synchronizer to signal the runner to restart after installation, at which time the runner will load the plugins.
This solution results in some wasted work because the runner starts after the deploy and is shortly thereafter restarted. A better solution will embed the installation work into the plugin runner so that plugins can be loaded into memory after installation without requiring a restart. That work will be in a different changeset.