From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v4 0/4] Support /run/* creation for initrc_t
Date: Wed, 29 Aug 2012 08:52:37 -0400 [thread overview]
Message-ID: <503E1095.9090307@tresys.com> (raw)
In-Reply-To: <20120825182417.GA23427@siphos.be>
On 08/25/12 14:24, Sven Vermeulen wrote:
> Due to the introduction of /run, many init scripts need to create the daemon run
> dirs (such as /run/udev for the udev init script). To simplify this, we
> introduce the "daemonrundir" attribute to which initrc_t has the necessary
> create_dirs_perms granted.
>
> Changes since v3
> ----------------
>
> - Add in setattr rights towards the daemonrundir types for initrc_t
> - Add in a couple of more identified domains that need this
> - Remove deprecation of previous functions, they are not used anymore, but not
> deprecated. The referred alternative (init_daemon_run_dir) is only when the
> methods were called for initrc_t.
This set merged. It think one minor additional tweak would have init_daemon_run_dir() to call files_pid_file() since the former is a subset of the latter.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2012-08-29 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 18:24 [refpolicy] [PATCH v4 0/4] Support /run/* creation for initrc_t Sven Vermeulen
2012-08-25 18:25 ` [refpolicy] [PATCH v4 1/4] Introduce init_daemon_run_dir transformation Sven Vermeulen
2012-08-25 18:25 ` [refpolicy] [PATCH v4 2/4] Use the init_daemon_run_dir interface for udev Sven Vermeulen
2012-08-25 18:26 ` [refpolicy] [PATCH v4 3/4] Allow initrc_t to create run dirs for core modules Sven Vermeulen
2012-08-25 18:26 ` [refpolicy] [PATCH v4 4/4] Allow initrc_t to create run dirs for contrib modules Sven Vermeulen
2012-08-25 22:42 ` Guido Trentalancia
2012-08-25 22:48 ` Sven Vermeulen
2012-08-29 12:52 ` Christopher J. PeBenito [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=503E1095.9090307@tresys.com \
--to=cpebenito@tresys.com \
--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.