Systemd in user session failes to launch starter service because SMACK blocks
access. It was caused by improper labeled systemd unit files with
"starter" label. This commit fixes it by labeling systemd specific files and
folders with "_" label.
In case of addition or moving systemd unit files, please label them with
"_" label.
Signed-off-by: Maciej Wereski <m.wereski@partner.samsung.com>
Name: starter
Summary: starter
Version: 0.4.56
-Release: 1
+Release: 2
Group: TO_BE/FILLED_IN
License: TO_BE/FILLED_IN
Source0: starter-%{version}.tar.gz
<filesystem path="/usr/bin/starter" label="starter" exec_label="starter" />
<filesystem path="/etc/init.d/rd3starter" label="_" exec_label="none" />
<filesystem path="/etc/init.d/rd4starter" label="_" exec_label="none" />
+ <filesystem path="/usr/lib/systemd/user/starter.path" label="_" exec_label="none" />
+ <filesystem path="/usr/lib/systemd/user/starter.service" label="_" exec_label="none" />
+ <filesystem path="/usr/lib/systemd/user/core-efl.target.wants/starter.path" label="_" exec_label="none" />
</assign>
</manifest>