From: Matthew Booth <mbooth@redhat.com>
To: linux-audit@redhat.com
Subject: audit_get_reply() returns EBADE
Date: Mon, 03 Mar 2008 11:26:44 +0000 [thread overview]
Message-ID: <47CBE074.9010706@redhat.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 725 bytes --]
A few times now I've seen audit_get_reply() return EBADE (Invalid
exchange). This coincides with a particular job which results in an
output rate of about 5.5k records/sec. The system remains responsive,
and it always fixes itself when the rate comes back down again.
What exactly does EBADE mean in this context? I assume I'm dropping
audit messages from the kernel while this is going on. Is there any way
I can determine how many? Is there any way to tune things to survive
this temporary stress event?
Thanks,
Matt
--
Matthew Booth, RHCA, RHCSS
Red Hat, Global Professional Services
M: +44 (0)7977 267231
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2008-03-03 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 11:26 Matthew Booth [this message]
2008-03-03 21:04 ` audit_get_reply() returns EBADE 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=47CBE074.9010706@redhat.com \
--to=mbooth@redhat.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 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.