What constitutes -f failure?

What constitutes -f failure?

[leam hall]

[-- Attachment #1.1: Type: text/plain, Size: 267 bytes --]

The -f flag is set to 0, 1, or 2 and specifies what to do on failure. Is
that "failure" any logging event? Or just logging events when the backlog
is higher than whatever the -b option sets it to?

Thanks!

Leam

-- 
Mind on a Mission <http://leamhall.blogspot.com/>

[-- Attachment #1.2: Type: text/html, Size: 405 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: What constitutes -f failure?

[Steve Grubb]

On Tuesday, October 29, 2013 03:51:53 PM leam hall wrote:
> The -f flag is set to 0, 1, or 2 and specifies what to do on failure. Is
> that "failure" any logging event? Or just logging events when the backlog
> is higher than whatever the -b option sets it to?
> 
> Thanks!
> 
> Leam

>From the auditctl man page:

              This option lets you 
              determine how you want the kernel  to  handle  critical  errors.
              Example conditions where this flag is consulted includes: trans‐
              mission  errors  to  userspace  audit  daemon,   backlog   limit
              exceeded,  out  of  kernel  memory, and rate limit exceeded. The
              default value is 1.

This is only for the kernel. User space error handling is dictated by the 
*_action settings in auditd.conf.

-Steve

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

Re: What constitutes -f failure?

[leam hall]

[-- Attachment #1.1: Type: text/plain, Size: 1056 bytes --]

Steve, thanks!

Leam


On Tue, Oct 29, 2013 at 4:17 PM, Steve Grubb <sgrubb@redhat.com> wrote:

> On Tuesday, October 29, 2013 03:51:53 PM leam hall wrote:
> > The -f flag is set to 0, 1, or 2 and specifies what to do on failure. Is
> > that "failure" any logging event? Or just logging events when the backlog
> > is higher than whatever the -b option sets it to?
> >
> > Thanks!
> >
> > Leam
>
> From the auditctl man page:
>
>               This option lets you
>               determine how you want the kernel  to  handle  critical
>  errors.
>               Example conditions where this flag is consulted includes:
> trans‐
>               mission  errors  to  userspace  audit  daemon,   backlog
> limit
>               exceeded,  out  of  kernel  memory, and rate limit exceeded.
> The
>               default value is 1.
>
> This is only for the kernel. User space error handling is dictated by the
> *_action settings in auditd.conf.
>
> -Steve
>



-- 
Mind on a Mission <http://leamhall.blogspot.com/>

[-- Attachment #1.2: Type: text/html, Size: 1639 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]