From: Steve Grubb <sgrubb@redhat.com>
To: Gisela Cheng <giselac@us.ibm.com>
Cc: linux-audit@redhat.com
Subject: Re: Fw: How to define rule for SERVICE_START/STOP?
Date: Tue, 05 Aug 2014 12:48:22 -0400 [thread overview]
Message-ID: <2027195.kI1qZKnNKp@x2> (raw)
In-Reply-To: <OFC7FB0EAB.C448828F-ON85257D2B.00499E1F-85257D2B.00503A04@us.ibm.com>
On Tuesday, August 05, 2014 10:36:17 AM Gisela Cheng wrote:
> Would this trigger the creation of the audit record?
I don't think anything in the config file would affect this. The requirements are
to record all starts and stops. I don't think it can record a segfault kind of
stop. That would, however, generate an ANOM_ABEND event.
> Our application is expected to be up and running all the time. But we can
> shut it down, or it could be down due to error. We want audit record when
> it is down. Would TimeoutStopSec= tag (don't know if this is the proper
> name) does it, or I need other special tag?
No tag should affect this.
-Steve
next prev parent reply other threads:[~2014-08-05 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 14:36 Fw: How to define rule for SERVICE_START/STOP? Gisela Cheng
2014-08-05 16:48 ` Steve Grubb [this message]
2014-08-06 12:57 ` Eric Paris
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=2027195.kI1qZKnNKp@x2 \
--to=sgrubb@redhat.com \
--cc=giselac@us.ibm.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