Refactoring csr.service and csr-OOO.socket 40/210240/3 accepted/tizen/unified/20190814.065142 submit/tizen/20190813.005155 submit/trunk/20190812.110839
authorINSUN PYO <insun.pyo@samsung.com>
Wed, 17 Jul 2019 06:34:50 +0000 (15:34 +0900)
committerINSUN PYO <insun.pyo@samsung.com>
Tue, 23 Jul 2019 10:59:06 +0000 (19:59 +0900)
commitd6e82e07cf995bb0035c84a289016b8ca66206e8
tree82d3815eccb2b4c09d016dfeed18b82009317a04
parent37afe06ea38163a714017aff1561b26ac3559e50
Refactoring csr.service and csr-OOO.socket

 - Using "Wants=csr.service" in csr-OOO.socket is replaced by putting csr.service in multi-user.target.wants.
 - Using "After=csr.service" in csr-OOO.socket is not requires because there is an explicit dependency between socket and service.
 - All four sockets are required for csr.service. So, "Requires=OOO.socket" must be in csr.service.
 - "Sockets=" in the csr.service is replaced by "Requires=OOO.socket". ("Sockets=" includes "After=" and "Wants=")

Change-Id: If6303fcf17f16c70b4c5b67cca897f0c650b4b85
packaging/csr-framework.spec
systemd/csr-admin.socket.in
systemd/csr-cs.socket.in
systemd/csr-wp.socket.in
systemd/csr.service.in