On 5/21/19 12:47 PM, Abhilash Raj wrote: > On Thu, May 16, 2019, at 5:45 AM, A. Schulze wrote: >> >> Q1: is there a better way to start mailman in some kind of non forking mode? >> Q2: is it possible to run mailman3 supervised? > > Yes, you can run the "master" command in Mailman 3 to run it in foreground > instead. That is what we do for Docker images. > > I am not super familiar with mailman 2, but it uses the same runners. Perhaps, > it is possible to do the same with mailman2?
Mailman 2 is different. There is no "master" command. mailmanctl forks itself and that becomes the master watcher which (re)starts the qrunners However, you can run qrunner --runner=All which will not fork and will just loop running all the qrunners in one process. I.e., instead of `mailmanctl start`, just run `qrunner --runner=All` which will run as a single process without forking. Note that this mode of operation is seldom used and may be buggy. In particular, see <https://bugs.launchpad.net/mailman/+bug/1818205> and <https://code.launchpad.net/~mluto/mailman/qrunnersleep/+merge/363767> -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
