From: russell@coker.com.au (Russell Coker)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] base monit policy
Date: Sun, 19 Feb 2017 21:07:50 +1100 [thread overview]
Message-ID: <201702192107.50397.russell@coker.com.au> (raw)
In-Reply-To: <19d23b60-f510-25a5-e80e-99a3c7517695@ieee.org>
On Sun, 19 Feb 2017 12:17:29 AM Chris PeBenito wrote:
> On 02/16/17 04:32, Russell Coker via refpolicy wrote:
> > Here is a patch for the monit policy without the monit_interactive_t
> > domain. This should be a minimally functional monit policy and we can
> > then build on it with the monit_interactive_t domain (or maybe a
> > different way of achieving the same goal).
> >
> >
> > From: cgzones <cgzones@googlemail.com>
> > Date: Fri, 25 Nov 2016 22:53:35 +0100
> > Subject: add monit module
> >
> > ---
> >
> > +
> > + init_get_all_units_status(monit_t)
> > + init_get_system_status(monit_t)
> > + init_start_all_units(monit_t)
> > + init_stop_all_units(monit_t)
> > + init_stream_connect(monit_t)
> > + ')
> > +')
>
> This patch looks ok, except for this part. Using the attribute like
> this isn't acceptable. Also, if systemd isn't enabled, this is an empty
> block, so the ifdef should be on the outside and tunable_policy nested
> inside.
OK, I've attached a new version that fixes this.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
-------------- next part --------------
An embedded message was scrubbed...
From: cgzones <cgzones@googlemail.com>
Subject: add monit module
Date: Fri, 25 Nov 2016 22:53:35 +0100
Size: 4451
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20170219/903933e2/attachment.mht
next prev parent reply other threads:[~2017-02-19 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 9:32 [refpolicy] [PATCH] base monit policy Russell Coker
2017-02-18 13:17 ` Chris PeBenito
2017-02-19 10:07 ` Russell Coker [this message]
2017-02-19 21:35 ` Chris PeBenito
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=201702192107.50397.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.