Imperial monitor plugins are incompatible with Broodlord mode

[francoisfreitag]

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.

For example, if the uWSGI config 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]

This can be worked around by adding a INI file for the Zerg configuration in the emperor directory (usually /etc/uwsgi.d) and telling the emperor to watch that directory. However, it partially negates the benefits of the emperor monitoring an external source, because it adds a dependency on the emperor filesystem.