On Monday 05 December 2005 09:54, Dustin Kirkland wrote:
This isn't bothering me yet, but something to think about if
there are
dozens of places in the kernel that start calling printk and audit_log.
The only places I want to get my hands on are: promiscuous mode change, quota
violations, and rlimit violations. Its a short list.
-Steve