1.5 later with no feedback, let's assume the tentative fix works.
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/387657
Title:
aa-logprof: doesn't handle large logs
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Binary package hint: apparmor
Ubuntu 8.04.2
Package: apparmor-utils
Version: 2.1+1075-0ubuntu9.2
My first experience with AppArmor was finding a kernel log file that
was full of 800 MB of AppArmor warnings from Samba and CUPS. I'm not
sure what suddenly enabled AppArmor on this LTS system, but while
fixing the problem I noticed....
aa-logprof, while processing an 800 MB log file, drove the load
average up into the high 40's. I suspect it was trying to load the
whole thing into memory (on a system with 1 GB of RAM). I'd recommend
revising the architecture so that it processes the lines as it sees
them.
I worked around the problem by splitting the file into a dozen 75MB
chunks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/387657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
