[MM3-users] Re: HyperKitty async tasks runner: systemd qcluster service fails eventually

There is another systemd service called mailman3-web.service provided by mailman3-web binary package:

# more /lib/systemd/system/mailman3-web.service
[Unit]
Description=Mailman3-web uWSGI service
After=network.target
Documentation=file:///usr/share/doc/mailman3-web/README.rst

[Service]
ExecStart=/usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini
Restart=on-failure
KillSignal=SIGQUIT
Type=notify
StandardError=syslog
NotifyAccess=all
User=root
Group=root

[Install]
WantedBy=multi-user.target

It also needs access to /var/log/mailman3/mailmansuite.log, so the final correct permissions for that file must be something like list:<gid> with <gid> being defined in /etc/mailman3/uwsgi.ini.

However, there is an attach-daemon = ./manage.py qcluster line which seems to perform the job of the previously defined qcluster.service, doesn't it?