From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: linux-audit@redhat.com
Cc: nikola.ciprich@linuxbox.cz
Subject: auditd 1.7.11 memory leak
Date: Tue, 24 Feb 2009 15:02:52 +0100 [thread overview]
Message-ID: <20090224140251.GB14730@develbox.linuxbox.cz> (raw)
Hi,
I noticed huge memory leak in auditd. If it's configured to NOT log any messages
(log_format = NOLOG), thus logging only via audisp plugins, its memory consumption starts
to grow. Running kernel compilations on system logging few system calls causes auditd memory
usage to grow over fer hundreds of MB in matter of tens of seconds...
I can provide more information if needed...
regards
nik
--
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next reply other threads:[~2009-02-24 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 14:02 Nikola Ciprich [this message]
2009-02-24 14:26 ` auditd 1.7.11 memory leak Steve Grubb
2009-02-24 20:56 ` Nikola Ciprich
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=20090224140251.GB14730@develbox.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=linux-audit@redhat.com \
--cc=nikola.ciprich@linuxbox.cz \
/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