Hide Forgot
Description of problem: I'm running script which causes SELINUX_ERR failure, but it is not reported in ~50% of cases. After some debugging, when I have added `sleep 3m` to the beginning of the script, I have found out, that when the script is started, there is: * running "readahead-collector" * not running "auditd" and 3 minutes later: * not running "readahead-collector" * running "auditd" When script is started after these 3 minutes, SELINUX_ERR nicely appears in /var/log/audit/audit.log. I have discussed it with Miroslav Trmac, and he said, that in the boot-time, readahead-collector replaces auditd and that readahead-collector might just drop messages he is not interested in. If this is exact, should readahead-collector be fixed, or should I keep mentioned workaround in my script (as I want that SELINUX_ERR to be reported)?
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
(In reply to comment #0) > Description of problem: > I'm running script which causes SELINUX_ERR failure, but it is not reported > in ~50% of cases. > > After some debugging, when I have added `sleep 3m` to the beginning of the > script, I have found out, that when the script is started, there is: > > * running "readahead-collector" > * not running "auditd" > > and 3 minutes later: > > * not running "readahead-collector" > * running "auditd" > > When script is started after these 3 minutes, SELINUX_ERR nicely appears in > /var/log/audit/audit.log. > > I have discussed it with Miroslav Trmac, and he said, that in the boot-time, > readahead-collector replaces auditd and that readahead-collector might just > drop messages he is not interested in. > > If this is exact, should readahead-collector be fixed, or should I keep > mentioned workaround in my script (as I want that SELINUX_ERR to be > reported)? You should just deinstall readahead.