Searched hist:f476683ce8493f1ae08d09bfaa3d579ffdb316f1 (Results 1 – 3 of 3) sorted by relevance
/openbmc/service-config-manager/inc/ |
H A D | srvcfg_manager.hpp | diff f476683ce8493f1ae08d09bfaa3d579ffdb316f1 Mon Feb 28 00:28:18 CST 2022 Jiaqing Zhao <jiaqing.zhao@intel.com> Improve socket-activated service handling
This patch provides a more generic way of handling socket-activated services like dropbear. A socket-activated service only has base socket unit and spawns service unit with instance name on incoming connection, so the instanced units of it need to be ignored. And whether a service is socket-activated can be determined by checking the existance of its service object path.
Tested: * Two socket-activated service, dropbear and obmc-console-ssh, can be controlled as expected. * Instances of socket-activated services are no loger added to monitor list.
Change-Id: If8faa2248e5794a410f804125410608aa69b858d Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.com>
|
/openbmc/service-config-manager/src/ |
H A D | srvcfg_manager.cpp | diff f476683ce8493f1ae08d09bfaa3d579ffdb316f1 Mon Feb 28 00:28:18 CST 2022 Jiaqing Zhao <jiaqing.zhao@intel.com> Improve socket-activated service handling
This patch provides a more generic way of handling socket-activated services like dropbear. A socket-activated service only has base socket unit and spawns service unit with instance name on incoming connection, so the instanced units of it need to be ignored. And whether a service is socket-activated can be determined by checking the existance of its service object path.
Tested: * Two socket-activated service, dropbear and obmc-console-ssh, can be controlled as expected. * Instances of socket-activated services are no loger added to monitor list.
Change-Id: If8faa2248e5794a410f804125410608aa69b858d Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.com>
|
H A D | main.cpp | diff f476683ce8493f1ae08d09bfaa3d579ffdb316f1 Mon Feb 28 00:28:18 CST 2022 Jiaqing Zhao <jiaqing.zhao@intel.com> Improve socket-activated service handling
This patch provides a more generic way of handling socket-activated services like dropbear. A socket-activated service only has base socket unit and spawns service unit with instance name on incoming connection, so the instanced units of it need to be ignored. And whether a service is socket-activated can be determined by checking the existance of its service object path.
Tested: * Two socket-activated service, dropbear and obmc-console-ssh, can be controlled as expected. * Instances of socket-activated services are no loger added to monitor list.
Change-Id: If8faa2248e5794a410f804125410608aa69b858d Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.com>
|