From: Richard Guy Briggs <rgb@redhat.com>
To: Aaron Lewis <the.warl0ck.1989@gmail.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: kauditd is writing too many lines in syslog
Date: Mon, 20 Jan 2014 12:36:27 -0500 [thread overview]
Message-ID: <20140120173627.GA1981@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAJZVxRmHA1+z45Qra28bmy1P+hkZzOOYczdpudr_YSoOJeJB7g@mail.gmail.com>
On 14/01/20, Aaron Lewis wrote:
> Hi,
>
> I'm not sure if this is the default behavior,
>
> I'm using audit 2.3.2, and I've configured auditd not to log anything
> (NOLOG option), and I set the queue buffer to 10240 messages.
I assume this is because you are using remote logging or using the
dispatcher?
> When the buffer is full or auditd is suddenly killed or for some other
> reason, it seems to write a lot of things to dmesg or
> /var/log/messages
This is by design.
> So, did kauditd wrote all these? I already killed auditd process but I
> can still see logs piling up.
If auditd has ever run, kaudit will continue to try delivering messages.
> Can I ask kauditd not print anything if user space program cannot
> handle that much message?
Sure, on the kernel boot line you can set audit=0 to disable kaudit, or
you can tell the init system to not start auditd.
> Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2014-01-20 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 4:45 kauditd is writing too many lines in syslog Aaron Lewis
2014-01-20 5:11 ` Aaron Lewis
2014-01-20 17:36 ` Richard Guy Briggs [this message]
2014-01-20 17:40 ` Steve Grubb
2014-01-20 18:24 ` Richard Guy Briggs
2014-01-20 18:34 ` Aaron Lewis
2014-01-20 20:43 ` Eric Paris
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=20140120173627.GA1981@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=the.warl0ck.1989@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.