`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/sec
/var/log/sec {
    missingok
    notifempty
    sharedscripts
    postrotate
        [ ! -f /run/sec.pid ] || kill -USR2 `cat /run/sec.pid`
    endscript
}

In the postrotate script, everything can be replaced by:

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

Because:

# systemctl show -P MainPID sec.service
1962
# cat /run/sec.pid
1962

Reproducible: Always




Additional Information:
sec-2.9.3-2.fc42.noarch