From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Compiling rules at boot when using systemd
Date: Sun, 23 Jun 2013 17:21:39 -0400 [thread overview]
Message-ID: <16533928.4VPka4HTtX@x2> (raw)
In-Reply-To: <20130523010648.4a6f4f32@fornost.bigon.be>
On Thursday, May 23, 2013 01:06:48 AM Laurent Bigonville wrote:
> Hello,
>
> I was wondering, the currently proposed solution to compile the rules
> when using systemd (copying the .services into /etc by hand) seems
> pretty hackish to me. Wouldn't it be better if there was a 2nd systemd
> .service file dedicated to call augenrules, disabled by default and
> depending against the main auditd.service file?
>
> This way the user could enable that new service instead of copying
> files by hand. This sounds better in distribution-wise and in cases
> changes are made to the .service file, the user will not be stuck with
> an old version in /etc.
>
> Any idea on this?
Not sure yet what the best approach is. Normally when restarting the audit
daemon you would get the latest rules loaded into the kernel. By separating
them, you wouldn't get that any more.
-Steve
prev parent reply other threads:[~2013-06-23 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 23:06 Compiling rules at boot when using systemd Laurent Bigonville
2013-06-23 21:21 ` Steve Grubb [this message]
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=16533928.4VPka4HTtX@x2 \
--to=sgrubb@redhat.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