diff options
author | Wang Quanyang <quanyang.wang@windriver.com> | 2018-08-17 11:01:37 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-08-20 11:59:44 +0100 |
commit | 3cb303ffee8610d41c9a0745d366556c24066bc3 (patch) | |
tree | 83321658206ceeb88ee1d11be1a49add9244abe3 /scripts/tiny | |
parent | f75289b9215580030540245cd0b5f945bfb05ffa (diff) | |
download | openembedded-core-3cb303ffee8610d41c9a0745d366556c24066bc3.tar.gz openembedded-core-3cb303ffee8610d41c9a0745d366556c24066bc3.tar.bz2 openembedded-core-3cb303ffee8610d41c9a0745d366556c24066bc3.zip |
weston-init: run login before start weston.service
When systemd start the weston.service, the script "weston-start" will
check if the dir "XDG_RUNTIME_DIR" (usually is /run/user/0) exits and
create it. Then weston will create a socket file "wayland-0" for communications
with clients in this dir.
If systemd is built with enabling "pam" feature, the login will call "run-user-0.mount"
to mount tmpfs at the dir "/run/user/0", then the socket file "wayland-0" will be
missing since it is created in the old "/run/user/0".
So add "PAMName=login" to let weston.service call login first, once tmpfs is mounted at
"/run/user/0", then call weston-start to create a socket file in it.
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/tiny')
0 files changed, 0 insertions, 0 deletions