`systemctl kill` leverages systemd's knowledge of the daemon's main PID, eliminating the need to rely on PID files or external tools like `killall` or `pkill`. This ensures precise signal sending to the intended process, reducing the risk of errors in process identification. Additionally, using `systemctl kill` logs the signal sending in the service's journal, providing a record of actions taken. Requires selinux-policy-41.43 or higher (see https://bugzilla.redhat.com/show_bug.cgi?id=2369644), available as an update for F41, F42, and Rawhide.

https://bodhi.fedoraproject.org/updates/FEDORA-2025-eb98eb9e24 (F41 -- will go to stable in a few days)
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f9f097f491 (F42 -- stable)
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3db4c0ec1c (Rawhide)

The logrotate configuration snippet:

# cat /etc/logrotate.d/mailman3
/var/log/mailman3/*.log {
    missingok
    sharedscripts
    su mailman mailman
    postrotate
        /bin/kill -HUP `cat /run/mailman3/master.pid 2>/dev/null` 2>/dev/null || true
        # Don't run "mailman3 reopen" with SELinux on here in the logrotate
        # context, it will be blocked
        #/usr/bin/mailman3 reopen >/dev/null 2>&1 || true
    endscript
}

In the postrotate script, kill can be replaced by:

/usr/bin/systemctl kill --signal=HUP --kill-whom=main mailman3.service 2>/dev/null || true

Because:

# systemctl show -P MainPID mailman3.service
2846
# cat /run/mailman3/master.pid
2846

Reproducible: Always




Additional Information:
mailman3-3.3.9-2.fc42.noarch