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
Sounds handy/convenient to address as a combined service via unit file. But I'm not as concerned about that. But if it were half a dozen or twenty or more ... but at a mere two, I'm not particularly concerned about that. And also, typically I wouldn't be bouncing mailman3 and mailman3-web services very regularly anyway. And if/when I am, well, there they are handy in the command history, so then quite super easy to do anyway. But yes, cool, handy idea - and would make things bit more goof resistant. I'd also be more inclined if there were two or six or more sysadmins managing it. But since it's mostly just me ...
But as for nntp yes, excellent catch on that! Total waste, so fixing that.
# ps axlwwwww | awk '{if((NR == 1) || /[Nn][Nn][Tt][Pp]/ ) print;}' F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 0 38 1371 1357 20 0 78004 3028 core_s S ? 1:21 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 # cd /etc/mailman3 # grep -a -F -i -e nntp mailman.cfg # ed mailman.cfg 11500 $ configuration: /etc/mailman3/mailman-hyperkitty.cfg a
[runner.nntp] start: no . w 11525 q # systemctl stop mailman3.service # systemctl start mailman3.service # ps axlwwwww | awk '{if((NR == 1) || /[Nn][Nn][Tt][Pp]/ ) print;}' F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND # ci -d -l -M -m'don'''t start nntp runner' mailman.cfg RCS/mailman.cfg,v <-- mailman.cfg new revision: 1.2; previous revision: 1.1 done #
And done!
On Sat, Aug 24, 2024 at 12:44 PM Ron / BCLUG admin@bclug.ca wrote:
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.