Onyeibo Oku writes:
I am happy to inform you that Systemd now starts and stops Mailman without interruptions.
Yay!
After series of SELinux file context labeling, setting the nis boolean, and a few custom policies, it resolved. Thank you for the responses (and your patience).
Perhaps you could post these to our wiki (https://wiki.list.org) if you don't consider them sensitive?
- Will there be a conflict of resource (ports, threads, etc) running another instance [of uwsgi]?
There can be. That's your problem, you need to configure each application to use non-conflicting ports and locations (URL paths, if the applications share externally-visible domains and ports). They can also conflict over internal resources such as file locks and I/O channels, but that depends on the specific applications. There are no conflicts among Mailman suite applications if configured as we recommend, but to know what conflicts might arise you need to explain what other apps will be running, and how you plan to configure them.
- Can one have multiple instances of uwsgi service?
You mean the same app running in parallel? That's probably not a good idea. If you mean several apps running in parallel, the answer is yes, provided you configure them not to conflict over resources.
In whichcase, it doesn't hurt to follow the doc to its logical conclusion?
I don't understand what you mean by logical conclusion.