From: sven.vermeulen@siphos.be (Sven Vermeulen) Date: Thu, 6 Sep 2012 19:35:38 +0200 Subject: [refpolicy] [PATCH v2 4/4] Allow init scripts to read courier configuration In-Reply-To: <1346952938-9358-1-git-send-email-sven.vermeulen@siphos.be> References: <1346952938-9358-1-git-send-email-sven.vermeulen@siphos.be> Message-ID: <1346952938-9358-5-git-send-email-sven.vermeulen@siphos.be> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com The courier-imap and courier-pop3 daemons are started by sourcing their configuration files, and then invoking the daemons using the proper options. If this is done through a specialized script, then init only needs to call this script (where a proper transition occurs) but if the init script itself does this, it needs to be able to read the configuration files. Signed-off-by: Sven Vermeulen --- policy/modules/system/init.te | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/policy/modules/system/init.te b/policy/modules/system/init.te index 0a7eda5..32dd043 100644 --- a/policy/modules/system/init.te +++ b/policy/modules/system/init.te @@ -613,6 +613,10 @@ optional_policy(` ') optional_policy(` + courier_read_config(initrc_t) +') + +optional_policy(` cpucontrol_stub(initrc_t) dev_getattr_cpu_dev(initrc_t) ') -- 1.7.8.6