[Bug 1035033] [NEW] bin/mailman --help could be improved
Public bug reported: What the "reopen" command does is not at all clear. (Is it like "reload" in an init script, rereading config files? If so, maybe "reload" would be a better name.) Presumably the "restart" command stops *and* starts the runners. You can assign this to me (it would be appreciated if you'd tell me what reopen does, although I guess I could read the code. :-) ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions
** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions
The 'reopen' command essentially causes the master watcher to SIGHUP the runner subprocesses. Right now all this does is reopen their log files, so it's there primarily to support log rotation. It would be nice if the runners could re-read their configuration files, but I suspect that will be difficult. Also, for correctness, the master should also re- read the configuration file. Yep, restart causes the master to SIGUSR1 all the runners. They exit, but with a status that the master recognizes as a restart, so it does. This does have the effect of reloading all the configuration files of course, but only for the runners, not for the master (though it may not matter much). Take a look at src/mailman/bin/runner.py for details. I'll assign this to you, unmilestoned. If you want to take a crack at config file reloaded, go for it, but if not (i.e. starting and stopping might be good enough), just mark this as Invalid. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Low => Wishlist ** Changed in: mailman Assignee: (unassigned) => Stephen Turnbull (stephen-xemacs) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions
I'm going to take a strict approach to this bug, and will attempt to improve the documentation. ** Changed in: mailman Status: Confirmed => In Progress ** Changed in: mailman Milestone: None => 3.0.0b3 ** Changed in: mailman Assignee: Stephen Turnbull (stephen-xemacs) => Barry Warsaw (barry) ** Changed in: mailman Importance: Wishlist => High ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions
** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions
participants (2)
-
Barry Warsaw -
Stephen Turnbull