| /openbmc/phosphor-state-manager/target_files/ |
| H A D | obmc-power-stop-pre@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-start-pre@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-force-warm-reboot@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-chassis-powered-off@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-warm-reboot@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-stopped@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-diagnostic-mode@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-stop-pre@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-stopping@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-power-off@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-chassis-hard-poweroff@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-power-on@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-started@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-starting@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-shutdown@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-reboot@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-start@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-power-stop@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-quiesce@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-chassis-poweroff@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-power-start-pre@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-power-start@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-stop@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-host-startmin@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|
| H A D | obmc-chassis-poweron@.target | diff 34b3b407d5d8dbc180c1356dd346f0b85e207ab2 Wed May 06 14:52:30 CDT 2020 Andrew Geissler <geissonator@yahoo.com> multi-user: do not use wants relationship
The multi-user target is run by systemd when the BMC first boots. It
contains all of the initial startup services. Some OpenBMC targets want
to ensure they are run after the multi-user target completes. A lot of
these targets did both a Wants and After relationship with multi-user.
The latest systemd, version 245, now takes that Wants relationship
seriously and will start any services within multi-user that are
stopped. This includes oneshot services which do not have the
"RemainAfterExit=yes" clause. If these services only expected to be run
once, as a part of multi-user, then they should include this clause but
you can see how they may expected to have only been run once.
The solution is twofold:
1) Fix the oneshot services that fall in the above scenario
2) Change the targets to not Wants=multi-user.target
1 will be changes throughout a few repositories.
2 is fixed in this commit.
Resolves openbmc/phosphor-state-manager#14
Tested:
Provided test image to George and he verified this fixed the above
issue
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6eb7e5d2cb7d5a3c95f2e8ef6efc708dbb63fd52
|