RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
usbguard-daemon.conf(5) states:

RuleFile=path
The USBGuard daemon will use this file to load the policy rule set from it and to write new rules received via the IPC interface. Default: %sysconfdir%/usbguard/rules.conf

But when starting usbguard.service with minimal configuration without RuleFile:

Aug 29 10:11:14 localhost.localdomain usbguard-daemon[3996]: [1661757074.047] (W) RuleFile not set; Modification of the permanent policy won't be possible.
Aug 29 10:11:14 localhost.localdomain usbguard-daemon[3996]: RuleFile not set; Modification of the permanent policy won't be possible.

Based on the man page and the message it is unclear whether the default is used or not? I think it would be better to allow for maximum flexibility and leave RuleFile undefined (or use /dev/null) instead of setting it to some value unconditionally, so perhaps only the man page needs tweaking in this regard.

Also, the message is needlessly logged twice in system log and the first line has unhelpful timestamp on it.

Version-Release number of selected component (if applicable):
usbguard-1.0.0-10.el9.x86_64

Regarding message duplication inside logs, you can turn off logging to console by adding "-K" option in the service file:
ExecStart=/usr/sbin/usbguard-daemon -f -s -K -c /etc/usbguard/usbguard-daemon.conf

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (usbguard bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2351