#
75ac2be3 |
| 22-Apr-2024 |
Anusha Dathatri <anusha.dathatri@gmail.com> |
chassis_service:Create /run/openbmc at start up
Create /run/openbmc directory on startup as other applications and services within phosphor-state-manager assume it to be already created. The chassis
chassis_service:Create /run/openbmc at start up
Create /run/openbmc directory on startup as other applications and services within phosphor-state-manager assume it to be already created. The chassis service is the best place to create the dir because it always runs first.
Fixes openbmc/phosphor-state-manager#22
Tested: Restarted daemon xyz.openbmc_project.State.Chassis@0.service and confirmed the presence of /run/openbmc directory
Change-Id: I7b9fedbbd50749e65e8bf8833da70c0422e4f4fe Signed-off-by: adathatri <anusha.dathatri@gmail.com>
show more ...
|
#
46068d9b |
| 14-Feb-2023 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
treewide: remove dependencies on mapper.target
The mapper is dbus activated now, so these explicit dependency declarations are unnecessary and redundant.
Change-Id: I9898fa6c9918a6ab4fe166acf5d335f
treewide: remove dependencies on mapper.target
The mapper is dbus activated now, so these explicit dependency declarations are unnecessary and redundant.
Change-Id: I9898fa6c9918a6ab4fe166acf5d335f89c1540fd Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
show more ...
|
#
a5eefd0f |
| 20-Jan-2023 |
Andrew Geissler <geissonator@yahoo.com> |
service-deps: remove logging as dependency
With the introduction of the following best practice: https://github.com/openbmc/docs/commit/43421bdd06dece37b2acc4c656d7839bfedcc681
It was determined th
service-deps: remove logging as dependency
With the introduction of the following best practice: https://github.com/openbmc/docs/commit/43421bdd06dece37b2acc4c656d7839bfedcc681
It was determined that phosphor-logging should be a d-bus activated service. That is, this service will be activated when called so there is no reason to specifically list it as a dependency in service files.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I8d871768bd3e515741825287bed4646a51c9b996
show more ...
|
#
70f36d8e |
| 14-Mar-2022 |
Potin Lai <potin.lai@quantatw.com> |
chassis-state-manager: Add multi-chassis support
Add multi-chassis management support, each chassis bus separates by giving a unique chassis id.
Current code only support single chassis, and alway
chassis-state-manager: Add multi-chassis support
Add multi-chassis management support, each chassis bus separates by giving a unique chassis id.
Current code only support single chassis, and alway assume bus name is "xyz.openbmc_project.State.Chassis".
This patch allow user to launch chassis-state-manager with a chassis id, and chassis id is added into service bus name for identification.
Because there are many places hardcode with bus name "xyz.openbmc_project.State.Chassis", if chassis id is 0, chassis-state-manager will request both "xyz.openbmc_project.State.Chassis" and "xyz.openbmc_project.State.Chassis0" bus name to meet backwards compatibility.
Tested on Bletchley: root@bletchley:~# busctl tree xyz.openbmc_project.State.Chassis `-/xyz `-/xyz/openbmc_project `-/xyz/openbmc_project/state `-/xyz/openbmc_project/state/chassis0 root@bletchley:~# busctl tree xyz.openbmc_project.State.Chassis0 `-/xyz `-/xyz/openbmc_project `-/xyz/openbmc_project/state `-/xyz/openbmc_project/state/chassis0 root@bletchley:~# busctl tree xyz.openbmc_project.State.Chassis1 `-/xyz `-/xyz/openbmc_project `-/xyz/openbmc_project/state `-/xyz/openbmc_project/state/chassis1 ......
patch dependencies: https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-state-manager/+/51465
Signed-off-by: Potin Lai <potin.lai@quantatw.com> Change-Id: I2ce3e9ab2c95a2688143f4e3775da164a5c33c19
show more ...
|