From: Steve Grubb <sgrubb@redhat.com>
To: "Bhagwat, Shriniketan Manjunath" <shriniketan.bhagwat@hpe.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Auditd reconfigure using SIGHUP
Date: Mon, 09 Jan 2017 09:04:02 -0500 [thread overview]
Message-ID: <1723559.Bc16368SjY@x2> (raw)
In-Reply-To: <CS1PR84MB02933378CF7D1F8B37BF649BFA640@CS1PR84MB0293.NAMPRD84.PROD.OUTLOOK.COM>
On Monday, January 9, 2017 1:30:57 PM EST Bhagwat, Shriniketan Manjunath wrote:
> Hi,
>
> Where can I see the changes?
This is the cumulative set of patches:
https://fedorahosted.org/audit/changeset?reponame=&new=1466%40trunk&old=1457%40trunk
> I tried to in the below location, however it's not.
>
> https://fedorahosted.org/audit/browser/branches/2.4/src
I have not added this to the 2.4 branch.
> https://github.com/linux-audit/audit-userspace/tree/master/src
This may not have sync'ed yet.
-Steve
> -----Original Message-----
> From: Steve Grubb [mailto:sgrubb@redhat.com]
> Sent: Monday, January 09, 2017 12:39 AM
> To: linux-audit@redhat.com
> Cc: Bhagwat, Shriniketan Manjunath <shriniketan.bhagwat@hpe.com>
> Subject: Re: Auditd reconfigure using SIGHUP
>
> Hello,
>
> On Friday, January 6, 2017 11:44:21 AM EST Steve Grubb wrote:
> > I tried this as a first step yesterday but what happens is the problem
> > gets worse. It thinks the dispatcher is running all the time and never
> > tries to restart it.
>
> Thanks for reporting this. Its fixed by upstream commits 1458 - 1466. There
> were quite a few issues in this section of the code.
>
> -Steve
prev parent reply other threads:[~2017-01-09 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 11:04 Auditd reconfigure using SIGHUP Bhagwat, Shriniketan Manjunath
2017-01-05 22:42 ` Steve Grubb
2017-01-06 6:29 ` Bhagwat, Shriniketan Manjunath
2017-01-06 16:44 ` Steve Grubb
2017-01-08 19:08 ` Steve Grubb
2017-01-09 13:30 ` Bhagwat, Shriniketan Manjunath
2017-01-09 14:04 ` Steve Grubb [this message]
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=1723559.Bc16368SjY@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=shriniketan.bhagwat@hpe.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;
as well as URLs for NNTP newsgroup(s).