projects / platform / core / security / security-manager.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ed455f0) | patch
Don't start the service on system boot, rely on socket activation 58/34458/4
authorRafal Krypa <r.krypa@samsung.com>
Tue, 27 Jan 2015 11:09:14 +0000 (12:09 +0100)
committerGerrit Code Review <gerrit@review.vlan103.tizen.org>
Thu, 5 Feb 2015 15:34:07 +0000 (07:34 -0800)
commit3a8e93b9741c6c0253ba1acbcdc6e5869cba6e5d
tree5350316f018c7ed6bdafbd12e615bbafb6ccb220tree | snapshot
parented455f0c98a862fe06adf5da6c9ba8089bc0c116commit | diff
Don't start the service on system boot, rely on socket activation

Security-manager doesn't need to be started immediately on system boot.
Systemd socket activation is already in place for lazy startup. Also previous
configuration wrongly started security-manager.target, which caused the
service to be launched without sockets passed from systemd.

Change-Id: I7bff7b58a4e016119e651edfefb85a2335b8b31f
Signed-off-by: Rafal Krypa <r.krypa@samsung.com>
packaging/security-manager.spec diff | blob | history
systemd/CMakeLists.txt diff | blob | history
systemd/security-manager.service.in diff | blob | history
systemd/security-manager.target [deleted file] blob | history
Domain: Security / Access Control;