On 07/31/2018 01:52 PM, Ryan McClung wrote:
That explains a lot. Is there any documentation you can provide to show me where I can set a static config/db?
See <http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html>
That may not specifically address your question, but it will explain the issue in detail. An example of what I do on several servers I support is this.
First, I install Mailman in a virtualenv which is /opt/mailman/mm/venv. Then the commands I run are all put in /opt/mailman/mm/bin. the actual installed 'mailman' command is /opt/mailman/mm/venv/bin/mailman but I never run that directly or as 'mailman' with the venv active. My var/ directory is /opt/mailman/mm/var. My mailman.cfg is actually outside of the var/ directory in /opt/mailman/mm/mailman.cfg. (In some cases for historical reasons it's in /opt/mailman/mm/deployment/mailman.cfg, but ignore that.)
In /opt/mailman/mm/bin/mailman, I have
#!/bin/bash unset PYTHONSTARTUP
exec /opt/mailman/mm/venv/bin/mailman
-C "/opt/mailman/mm/mailman.cfg"
$@
The details such as installing in a venv or where things are are not the important things. The important thing is the only 'mailman' command I ever run invokes Mailman with a -C option that points to the only config I want to use and that in turn has a var_dir setting pointing to, in my case, /opt/mailman/mm/var.
Also, the 'unset PYTHONSTARTUP' is there to address an issue with 'mailman shell' that would double the size of the shell history file each time it was run. I'm not certain that's still needed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan