From: "Timothy R. Chavez" <tim.chavez@linux.vnet.ibm.com>
To: Ameel Kamboh <akamboh@nortel.com>
Cc: linux-audit@redhat.com
Subject: Re: Audit messages on console
Date: Fri, 03 Aug 2007 14:08:12 -0500 [thread overview]
Message-ID: <1186168092.27344.22.camel@localhost.localdomain> (raw)
In-Reply-To: <1186167288.27344.20.camel@localhost.localdomain>
On Fri, 2007-08-03 at 13:54 -0500, Timothy R. Chavez wrote:
> On Fri, 2007-08-03 at 13:26 -0500, Ameel Kamboh wrote:
> > I notice that if the auditd service is not running,
> > I see all my audit logs go out on the console,
> > When I start auditd service they go to the appropriate log file.
> > Is there a way to turn this off in the kernel?
> >
>
> Hi Ameel,
>
> If audit is enabled, but auditd isn't running, the audit records will be
> delivered to userspace via printk (KERN_NOTICE <5>). So perhaps you'll
> just need to edit /etc/sysconfig and route kern.5 accordingly? If you
Erm, /etc/syslog.conf
-tim
next prev parent reply other threads:[~2007-08-03 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 18:26 Audit messages on console Ameel Kamboh
2007-08-03 18:54 ` Timothy R. Chavez
2007-08-03 19:08 ` Timothy R. Chavez [this message]
2007-08-03 19:10 ` Stephen John Smoogen
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=1186168092.27344.22.camel@localhost.localdomain \
--to=tim.chavez@linux.vnet.ibm.com \
--cc=akamboh@nortel.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