On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote:
On 09/21/2017 01:29 PM, Andrew Hodder wrote:
I keep getting around this by creating symlinks to the pid file and then the stop works, but it's getting silly. It seems like mailman just assumes CWD + /var/ + master.pid must be the location. Once I realized this, I found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since it'd then add /var/master.pid). But that seems a little nonsensical.
That is the normal expected behavior if devmode is enabled. Check your configs for this.
I don't think devmode has anything to do with this, it only disables
sending out emails by accident and routes all emails to a pre-defined
address. Haven't looked at the relevant portion of the source so I might
be wrong.
In the absence of any configuration file in pre-defined locations1,
Core will always generate a var/ directory under $CWD with basic
configuration and use it to track a running mailman instance (logs, db,
pid file etc).
Ideally, you should place your configuration file at one of the
locations that it looks and specify a [paths.custom] directive in
there to make sure it knows where to put everything. See 2 for more
details.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in