On Thu, May 16, 2019, at 5:45 AM, A. Schulze wrote:
Hello,
I'm porting a mailman installation from a legacy server into docker. To make it not more complicated I decided to stay on the same mailman
version 2.1.29 (build from source)Now I'm faced to the problem that mailman is started with "mailmanctl start" This fork a daemon running in background. In an ideal docker world
there is only one process per container. If the process return/end, the container terminate.For now I solved this by running "fghack mailmanctl start" fghack -> https://cr.yp.to/daemontools/fghack.html
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?
Thanks! Andreas
Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-leave@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
-- thanks, Abhilash Raj (maxking)