[oe-commits] [openembedded-core] 09/15: psplash: Fix systemd service dependencies

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a commit to branch master-next
in repository openembedded-core.

commit 9c140b2ed5eff33fb2d93af0460eec7d58d88881
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
AuthorDate: Sat Feb 22 13:55:25 2020 +0000

    psplash: Fix systemd service dependencies
    
    Avoid:
    qemux86-64 psplash-systemd[135]: Error unable to open fifo
    
    by adding the missing dependency on /run/ where the fifo resides.
    
    Also, psplash-systemd requires psplash-start, not the other way around
    as the splash creates the fifo which the other then needs to open.
    
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 meta/recipes-core/psplash/files/psplash-start.service   | 2 +-
 meta/recipes-core/psplash/files/psplash-systemd.service | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/psplash/files/psplash-start.service b/meta/recipes-core/psplash/files/psplash-start.service
index 9de8f63..af9d5d6 100644
--- a/meta/recipes-core/psplash/files/psplash-start.service
+++ b/meta/recipes-core/psplash/files/psplash-start.service
@@ -1,7 +1,7 @@
 [Unit]
 Description=Start psplash boot splash screen
 DefaultDependencies=no
-Requires=psplash-systemd.service
+RequiresMountsFor=/run
 
 [Service]
 ExecStart=/usr/bin/psplash
diff --git a/meta/recipes-core/psplash/files/psplash-systemd.service b/meta/recipes-core/psplash/files/psplash-systemd.service
index e14f420..249aa54 100644
--- a/meta/recipes-core/psplash/files/psplash-systemd.service
+++ b/meta/recipes-core/psplash/files/psplash-systemd.service
@@ -2,6 +2,8 @@
 Description=Start psplash-systemd progress communication helper
 DefaultDependencies=no
 After=systemd-start.service
+Requires=psplash-start.service
+RequiresMountsFor=/run
 
 [Service]
 ExecStart=/usr/bin/psplash-systemd

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.