Warn imperial monitors plugins are incompatible with Broodlord #470
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `uwsgi_emperor_spawn_vassal()` function is responsible for starting new vassals. It constructs arguments for the vassal in the `vassal_new_argv()` function, based on the configuration file extension [1]. For example, if the uWSGI configuration file is named `django-001.ini`, it passes `--ini django-001.ini` to the new vassal. The Zergs thus expect to find their config in the emperor filesystem directory. Since the INI file does not exist, Zergs are prevented from spawning and complain with: ``` realpath() of django-001.ini failed: No such file or directory [core/utils.c line 3651] ``` More details are available in unbit/uwsgi#2166. [1] https://github.com/unbit/uwsgi/blob/d22a189c4dce0c1f90c31b9687902572d9d0b438/core/emperor.c#L115-L134
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
uwsgi_emperor_spawn_vassal()function is responsible for startingnew vassals. It constructs arguments for the vassal in the
vassal_new_argv()function, based on the configuration file extension[1].
For example, if the uWSGI configuration file is named
django-001.ini,it passes
--ini django-001.inito the new vassal. The Zergs thusexpect to find their config in the emperor filesystem directory. Since
the INI file does not exist, Zergs are prevented from spawning and
complain with:
More details are available in
unbit/uwsgi#2166.
[1] https://github.com/unbit/uwsgi/blob/d22a189c4dce0c1f90c31b9687902572d9d0b438/core/emperor.c#L115-L134