summaryrefslogtreecommitdiff
path: root/src/mailman/interfaces/command.py
diff options
context:
space:
mode:
authorBarry Warsaw2010-03-28 17:04:59 -0400
committerBarry Warsaw2010-03-28 17:04:59 -0400
commite2e024972d130f919890bb84aeab02354e0ff5c1 (patch)
tree06674f1e96f67ccaa20cd903f302dae85f2e4f25 /src/mailman/interfaces/command.py
parent9b3e3881f4db1de7deca487859afff22aa922324 (diff)
downloadmailman-e2e024972d130f919890bb84aeab02354e0ff5c1.tar.gz
mailman-e2e024972d130f919890bb84aeab02354e0ff5c1.tar.zst
mailman-e2e024972d130f919890bb84aeab02354e0ff5c1.zip
More fixes to the start up procedure. The root cause of the fix is that when
var_dir in the config file is a relative path, the bin/master and bin/qrunner subprocesses end up creating another hierarchy under $VAR_DIR. This is because 'bin/mailman start' chdirs to $VAR_DIR before starting master. The fix involves putting the absolute path to $VAR_DIR in the $MAILMAN_VAR_DIR environment variable. If the configuration file reader sees this, it uses the value instead of $var_dir from the configuration file. Another change is to remove qrunner's --subproc/-s option and stick this in the environment as well, using $MAILMAN_UNDER_MASTER_CONTROL. Other fixes here include: * Deciphering the master lock file contents correctly * Reformatting the error message so that it fits in 79 columns when prefixed by argparse error info.
Diffstat (limited to 'src/mailman/interfaces/command.py')
0 files changed, 0 insertions, 0 deletions