Created attachment 869495 [details] setroubleshoot logspam example Every time there's an AVC, every time I click on setroubleshoot, many many lines spam my system log. I understand logs makes it easier to debug, but this amount of logging is (for a lack of a nicer word) unacceptable. This verboisty is a "debug" level and should not be used by default. Please either stop spamming the system log, or at least disable this by default (add a --debug flag or something). This amount of output in the system log makes it harder to debug other applications, and makes the log almost unreadble, hiding informative data in a huge pile of setroubleshoot debugging data (which is not useful unless you are actually debugging setroubleshoot).
I believe these are at debug level. I am not seeing these messages in my log files. Are you certain you have not turned on syslog to log debug messages?
I don't have syslog here, only systemd-journald with the default settings.
If systemd-journald takes all debug messages from syslog, I am not sure what I need to do.
I'd say don't output any debug messages unless a debug flag is set.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
I believe that this is fixed in setroubleshoot-3.2.18-1, upstream commit https://github.com/fedora-selinux/setroubleshoot/commit/37d80af2f97917191d73f82011af7cdf33e58d40