Michael Paoli via BALUG-Test wrote on 2024-08-23 05:29:
restarted the relevant service: # systemctl stop mailman3-web.service # systemctl start mailman3-web.service
This reminded me - I've modified my unit files so that only one service needs be started - same for re-starting or stopping:
Create a file at
/etc/systemd/system/mailman3.service.d/override.conf
with these contents:
[Unit] Upholds = mailman3-web.service Before = mailman3-web.service
Probably need a `systemctl daemon-reload` for systemd to read it.
Now, starting mailman3.service will *also* start mailman3-web.service. Now, restarting mailman3.service will *also* restart mailman3-web.service. Now, stopping mailman3.service will *also* stop mailman3-web.service.
Also, there's really no need for nntp bridging IMHO, but it's enabled by default. Which causes an extra entire Python interpreter to be loaded in to memory.
Disable this via:
/etc/mailman3/mailman.cfg
[runner.nntp] start: no
Save some RAM...
I believe this nntp support will be removed from default settings in the future, since I called attention to it on MM3 mailing list.
rb