[Bug 925559] Re: Mailman Masterrunner keeps locks after force
925559 at bugs.launchpad.net
Sun Apr 8 00:18:20 CEST 2012
I think this is user error. `bin/mailman start` is just a little front-
end that forks and execs the actual master script. This runs in the
background and detaches itself from the controlling terminal, so exiting
the terminal is not meant to stop the master, or any of its own
subprocesses. I think the locks aren't getting deleted because
everything's still running.
You should not use --force in this case. Only use --force when you know
the master is no longer running. Use `bin/mailman status` to find that
out. In your case, just open up a new terminal and run `bin/mailman
stop` and everything should work properly.
** Changed in: mailman
Status: Triaged => Invalid
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Mailman Masterrunner keeps locks after force
To manage notifications about this bug go to:
More information about the Mailman-coders