op-occ-start/stop should not impact host targets

There have been some situations where things get so messed up that
starting or stopping the occ monitoring on the BMC will fail. When
this happens, the systemd target, obmc-host-start/stop can not
complete. This really should be a wants relationship vs. a requires
so that the targets can continue to start/stop the host. The service
is not required to start/stop the host.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I42e1651a2d1b78b096582bc0e09b3b682bae726e
1 file changed
tree: c49d0f04868f453e83c6bf7e6e1f3b5e6628ab4b
  1. classes/
  2. conf/
  3. recipes-bsp/
  4. recipes-devtools/
  5. recipes-phosphor/
  6. COPYING.apache-2.0
  7. COPYING.MIT
  8. LICENSE
  9. MAINTAINERS
  10. README.md
README.md

OpenEmbedded/Yocto/OpenBMC BSP layer for OpenPOWER reference platforms

This layer provides support for the BMC firmware on OpenPOWER reference platforms, and/or a base upon which to create a BMC firmware implementation on any POWER system.

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
layers: meta
branch: master
revision: HEAD

URI: https://github.com/openbmc/meta-phosphor
branch: master
revision: HEAD

URI: https://github.com/openbmc/meta-aspeed
branch: master
revision: HEAD

More information on OpenPOWER can be found here.

Contributing

meta-openpower patches are reviewed using the Gerrit instance at https://gerrit.openbmc-project.xyz.

Please submit patches to Gerrit. More information on using Gerrit can be found here. https://github.com/openbmc/meta-openpower is a hosting mirror only and GitHub pull requests are not monitored and will not be accepted.

Patch checklist. Please ensure patches adhere to the following guidelines:

For questions or help please come join us on the mailing list or in IRC.