@@ -758,23 +758,24 @@ activation, an accompanying systemd socket unit file
Documentation=https://sbabic.github.io/swupdate
[Socket]
- ListenStream=/tmp/sockinstctrl
- ListenStream=/tmp/swupdateprog
+ ListenStream=/run/sockinstctrl
+ ListenStream=/run/swupdateprog
[Install]
WantedBy=sockets.target
On ``swupdate.socket`` being started, systemd creates the socket
files and hands them over to SWUpdate when it starts. So, for
-example, when talking to ``/tmp/swupdateprog``, systemd starts
+example, when talking to ``/run/swupdateprog``, systemd starts
``swupdate.service`` and hands-over the socket files. The socket
files are also handed over on a "regular" start of SWUpdate via
``systemctl start swupdate.service``.
-Note that the socket paths in the two ``ListenStream=`` directives
-have to match the socket paths ``CONFIG_SOCKET_CTRL_PATH`` and
-``CONFIG_SOCKET_PROGRESS_PATH`` in SWUpdate's configuration.
-Here, the default socket path configuration is depicted.
+Note, that all dependent services need to access the swupdate
+sockets via the paths specified in the ``swupdate.socket`` systemd
+unit. The paths used in the example from above are not the default
+swupdate socket paths, but follow the recommended directory
+structure proposed by systemd.
.. _systemd: https://www.freedesktop.org/wiki/Software/systemd/
When running under systemd, the proposed paths for sockets are below /run and not /tmp, as /tmp is always world writable. In addition, the note about default paths is changed, as there are various methods to control the location where clients expect the swupdate sockets. Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com> --- doc/source/swupdate.rst | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-)