On Mon, 2020-12-21 at 12:14 -0600, Richard Shaw wrote:
> It looks like this has been a problem for a while but I only just now
> noticed.
> Is it really necessary to have all the audit: messages in dmesg? It
> makes it nearly unreadable.
I revisited
On Mon, Dec 21, 2020 at 1:43 PM Gary Buhrmaster
wrote:
> On Mon, Dec 21, 2020 at 7:25 PM Richard Shaw wrote:
>
> > I would say so...
> >
> > $ dmesg | grep -c audit
> > 767
> >
> > $ dmesg | grep -cv audit
> > 30
> >
>
> You will likely have to share some of the audit
> entries.
>
I don't want
On Mon, Dec 21, 2020 at 7:25 PM Richard Shaw wrote:
> I would say so...
>
> $ dmesg | grep -c audit
> 767
>
> $ dmesg | grep -cv audit
> 30
>
You will likely have to share some of the audit
entries.
That last time I recall seeing so many audit entries
in dmesg I had set selinux to be
On Mon, Dec 21, 2020 at 12:54 PM Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:
> Hello Richard,
>
> Right after logging in (and starting Firefox), dmesg returns 1176
> lines, of which 25 are audit messages. It's pretty much the same ratio
> on a second desktop and slightly higher
Hello Richard,
Right after logging in (and starting Firefox), dmesg returns 1176
lines, of which 25 are audit messages. It's pretty much the same ratio
on a second desktop and slightly higher (46/724) on a server running
multiple services, but I would call neither nearly unreadable. Are you
