From: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
To: linux-audit@redhat.com
Subject: Re: mode = forward
Date: Mon, 30 Jul 2012 10:17:09 -0300 [thread overview]
Message-ID: <50168955.9010307@linux.vnet.ibm.com> (raw)
In-Reply-To: <1343524923.2542.18.camel@debian.domain_name>
Hi Michael,
Which component is complaining that the queue is full, audispd or
audisp-remote? audisp-remote is used for remote logging and I'm not sure
if this is your case. Can you provide us more information about this?
I took a quick look at the source code of version 1.7.18 of
audisp-remote and it actually just supports "immediate" mode. Probably
"forward" mode is supported by lately versions.
If audispd is complaining about its queue (instead of audisp-remote),
you can try to increase the value of q_depth in the audispd.conf file.
Regards,
Marcelo
On 07/28/2012 10:22 PM, Michael Mather wrote:
> I am using Ubuntu 12.04, which uses version 1.7.18 of auditd.
>
> Audispd is complaining that the queue is full and it is dropping events.
>
> According to the man page for audisp-remote.conf (as found at
> linux.die.net), the parameter "mode" can be set to "immediate" or
> "forward". "forward" means that events are buffered in a queue.
>
> I found that "mode" was set to "immediate", and the queue did not exist.
>
> But when I try to set the value as "forward" and restart auditd,
> audisp-remote complains that "Option forward not found". And the queue
> still gets full.
>
> Last October, Steve was writing about how big the queue might be on this
> very site.
>
> Can someone explain what is going on?
>
> Thanks - Michael
> ----------------
>
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
>
next prev parent reply other threads:[~2012-07-30 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 1:22 mode = forward Michael Mather
2012-07-30 13:17 ` Marcelo Cerri [this message]
2012-07-30 14:00 ` Michael Mather
2012-07-30 14:24 ` Steve Grubb
2012-07-30 18:50 ` Michael Mather
2012-07-30 14:14 ` Steve Grubb
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=50168955.9010307@linux.vnet.ibm.com \
--to=mhcerri@linux.vnet.ibm.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