Avahi:Fix to check and create avahi group and user before starting avahi
service.

Avahi service fails to start when we code update from image which has no
avahi service to image which has avahi service,As part of code update.
we don't touch the persistent file(/etc/group or /etc/password).
Now the image which is going to be updated needs these persistent files
to be updated.

I have tried to add avahi user using extrausers and pkg_postinst scripts
I could see updated /etc/group and /etc/password files with avahi entry
in rootfs build directory, but after code update to this new BMC image
we dont see these udpated files on the system, where as this new image
requires avahi user and the group to be present in the /etc/passwd and
/etc/group on the system.

Implemented service override file to check and create avahi group
and user before starting avahi service.

Tested By:
1.Code updating images
2.Reboot

Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
Change-Id: I797333404dad515a1bd8c22833ff73c3316e3216
2 files changed
tree: 271a727ef22b360d30fe5c407f3c207994f4002b
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. COPYING.apache-2.0
  16. COPYING.MIT
  17. LICENSE
  18. MAINTAINERS
  19. README.md
  20. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.