On Monday, November 13, 2017 8:12:44 PM EST warron.french wrote:
> So, I wonder why I am having a problem on lone #65 then.
Because it's a duplicate of 58.
> Or does the error actually mean after line 65?
Nope. It means 65. Just delete one or the other and you should be fine.
-Steve
> On Mon,
So, I wonder why I am having a problem on lone #65 then. Or does the error
actually mean after line 65?
Thanks,
--
Warron French
On Mon, Nov 13, 2017 at 3:12 PM, Steve Grubb wrote:
> On Friday, November 10, 2017 1:32:34 PM EST warron.french wrote:
> > Steve, can you h
the function comments (2017-09-05 09:46:59 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
tags/audit-pr-20171113
for you to fetch changes up to 42d5e37654e4cdb9fb2e2f3ab30045fee35c42d8:
audit: filter PATH records keyed on
On Friday, November 10, 2017 1:32:34 PM EST warron.french wrote:
> Steve, can you help me with this please?
> Somehow this slipped past our QA process, but I have an error popping up in
> */var/log/boot.log* indicating:
>
> *28* Starting auditd: ^[[60G[^[[0;32m OK ^[[0;39m]^M
> * 29* Error send
On Mon, Nov 13, 2017 at 1:30 PM, Steve Grubb wrote:
> On Thursday, November 9, 2017 3:52:46 PM EST Richard Guy Briggs wrote:
>> > >> > It might be simplest to just apply a corrective patch over top of
>> > >> > this one so that you don't have to muck about with git branches and
>> > >> > commit me
On Thursday, November 9, 2017 3:52:46 PM EST Richard Guy Briggs wrote:
> > >> > It might be simplest to just apply a corrective patch over top of
> > >> > this one so that you don't have to muck about with git branches and
> > >> > commit messages.
> > >>
> > >> A quick note on the "corrective pat