From 789e474ddbd76da44bef15f7c0de5541cb09eae7 Mon Sep 17 00:00:00 2001 From: Philipp Zabel Date: Thu, 29 Jun 2023 16:06:14 +0200 Subject: [PATCH] doc: Add systemd-notify.so module to systemd unit example Closes: https://gitlab.freedesktop.org/wayland/weston/-/issues/767 Signed-off-by: Philipp Zabel --- doc/sphinx/toc/running-weston.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/sphinx/toc/running-weston.rst b/doc/sphinx/toc/running-weston.rst index f1e1d59a7..651241283 100644 --- a/doc/sphinx/toc/running-weston.rst +++ b/doc/sphinx/toc/running-weston.rst @@ -194,6 +194,8 @@ rather than as systemd system service, still relying on logind launcher. In order to do that we would need two `unit `_ files, a ``.service`` and a ``.socket`` one. +The ``systemd-notify.so`` module needs to be enabled to notify systemd when +Weston has finished its startup and is ready to accept client connections. On a Debian system, the systemd user units are under ``/etc/systemd/user/`` directory. @@ -236,7 +238,7 @@ directory. StandardError=journal # add a ~/.config/weston.ini and weston will pick-it up - ExecStart=/usr/bin/weston + ExecStart=/usr/bin/weston --modules=systemd-notify.so [Install] WantedBy=graphical-session.target