From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2 0/3] Using init_daemon_pid_file
Date: Thu, 26 Jun 2014 08:38:20 -0400 [thread overview]
Message-ID: <53AC143C.90504@tresys.com> (raw)
In-Reply-To: <1403725982-10043-1-git-send-email-sven.vermeulen@siphos.be>
On 6/25/2014 3:52 PM, Sven Vermeulen wrote:
> This patchset introduces the init_daemon_pid_file interface, deprecates init_daemon_run_dir and updates the non-contrib modules to use the new init_daemon_pid_file interface.
This set can be merged, but I need the patch(es) for contrib too.
> Changes since v1:
> - Do not remove old attribute yet, keep it for backwards compatibility
>
> Sven Vermeulen (3):
> Support initrc_t generated pid files with file transition
> Deprecate init_daemon_run_dir interface
> Use init_daemon_pid_file instead of init_daemon_run_dir
>
> policy/modules/services/postgresql.te | 2 +-
> policy/modules/services/ssh.te | 2 +-
> policy/modules/system/init.if | 38 ++++++++++++++++++++++++++++++++---
> policy/modules/system/init.te | 8 ++++++++
> policy/modules/system/setrans.te | 2 +-
> policy/modules/system/sysnetwork.te | 2 +-
> policy/modules/system/udev.te | 2 +-
> 7 files changed, 48 insertions(+), 8 deletions(-)
>
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-06-26 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 19:52 [refpolicy] [PATCH v2 0/3] Using init_daemon_pid_file Sven Vermeulen
2014-06-25 19:53 ` [refpolicy] [PATCH v2 1/3] Support initrc_t generated pid files with file transition Sven Vermeulen
2014-06-25 19:53 ` [refpolicy] [PATCH v2 2/3] Deprecate init_daemon_run_dir interface Sven Vermeulen
2014-06-25 19:53 ` [refpolicy] [PATCH v2 3/3] Use init_daemon_pid_file instead of init_daemon_run_dir Sven Vermeulen
2014-06-26 12:38 ` Christopher J. PeBenito [this message]
2014-06-30 18:37 ` [refpolicy] [PATCH v2 0/3] Using init_daemon_pid_file Christopher J. 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=53AC143C.90504@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.