Bug 2181137

Summary: Default q_size doesn't match manpage's one
Product: Red Hat Enterprise Linux 8 Reporter: Renaud Métrich <rmetrich>
Component: fapolicydAssignee: Radovan Sroka <rsroka>
Status: CLOSED MIGRATED QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: low    
Version: 8.7CC: qguo
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2215524 (view as bug list) Environment:
Last Closed: 2023-06-19 17:37:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2215524    

Description Renaud Métrich 2023-03-23 08:16:21 UTC
Description of problem:

By default `/etc/fapolicyd/fapolicyd.conf` has a 640 long queue:
~~~
q_size = 640
~~~

But manpage states the default is 1024:
~~~
       q_size This option is used to control how big of an internal queue that fapolicyd will use. If requests come
              in faster than fapolicyd can answer, the queue holds the pending requests. If the  do_stat_report  is
              enabled,  when fapolicyd shutsdown it will provide some statistics which includes maximum queue depth
              used. This information can be used to help tune performance. The default value is 1024.
~~~

I think the configuration file should be aligned.

Additionally there is a small typo in the manpage:

"when fapolicyd shutsdown it will provide"
                ^^^^^^^^^

Version-Release number of selected component (if applicable):

fapolicyd-1.1.3-8.el8_7.1.x86_64

How reproducible:

N/A

Comment 1 Radovan Sroka 2023-06-19 17:32:35 UTC
This bug is going to be migrated.

Contact point for migration questions or issues: rsroka
Guidance for Bugzilla users to test their Jira account or create one if needed:

https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016394
https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016694
https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016774