From: Ian Pilcher <arequipeno@gmail.com>
To: linux-audit@redhat.com
Subject: Re: "write_logs = no" not working
Date: Mon, 6 Mar 2017 14:57:14 -0600 [thread overview]
Message-ID: <o9kif4$bnh$1@blaine.gmane.org> (raw)
In-Reply-To: <20170306083459.1e7f81e9@ivy-bridge>
On 03/06/2017 07:34 AM, Steve Grubb wrote:
> There was a z-stream audit package shipped last week that fixes this. I
> suspect it hasn't worked its way through Centos just yet. You can pick
> up the srpm in koji if you're in a hurry.
Building now (very slowly on a non-accelerated QEMU armv7 VM). It looks
like the update has made it to CentOS x86_64, but not ARM.
--
========================================================================
Ian Pilcher arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================
next prev parent reply other threads:[~2017-03-06 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 2:38 "write_logs = no" not working Ian Pilcher
2017-03-06 13:34 ` Steve Grubb
2017-03-06 20:57 ` Ian Pilcher [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-06 3:22 Ian Pilcher
2017-03-06 4:22 ` Stephen Buchanan
2017-03-06 4:33 ` Ian Pilcher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='o9kif4$bnh$1@blaine.gmane.org' \
--to=arequipeno@gmail.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox