mirrors/weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Add systemd-notify.so module to systemd unit example

Browse Source 
Closes: https://gitlab.freedesktop.org/wayland/weston/-/issues/767

Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
This commit is contained in:
Philipp Zabel 2023-06-29 16:06:14 +02:00
parent 25ffc4ae92
commit 789e474ddb
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/sphinx/toc/running-weston.rst
View File

@ -194,6 +194,8 @@ rather than as systemd system service, still relying on logind launcher. In
order to do that we would need two order to do that we would need two
`unit <https://man7.org/linux/man-pages/man5/systemd.unit.5.html>`_ files, `unit <https://man7.org/linux/man-pages/man5/systemd.unit.5.html>`_ files,
a ``.service`` and a ``.socket`` one. 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/`` On a Debian system, the systemd user units are under ``/etc/systemd/user/``
directory. directory.
@ -236,7 +238,7 @@ directory.
StandardError=journal StandardError=journal
# add a ~/.config/weston.ini and weston will pick-it up # add a ~/.config/weston.ini and weston will pick-it up
ExecStart=/usr/bin/weston ExecStart=/usr/bin/weston --modules=systemd-notify.so
[Install] [Install]
WantedBy=graphical-session.target WantedBy=graphical-session.target