fix(systemd): always use socket activation

foot --server supports socket activation when managed by systemd or s6,
so remove the Install section from the .service unit to make systemd
always use socket activation for the service.

Also mention in the foot(1) manpage how to easily enable the
systemd-managed foot server.

See <https://codeberg.org/dnkl/foot/pulls/1110#issuecomment-661389>
This commit is contained in:
Andrea Pappacoda 2022-10-28 21:37:20 +02:00
parent 59c9dfe109
commit e2d67af8ed
No known key found for this signature in database
GPG key ID: 4A9208A2455077A7
2 changed files with 5 additions and 4 deletions

View file

@ -123,7 +123,11 @@ the foot command line
Two systemd units (foot-server@.{service,socket}) are provided to use that Two systemd units (foot-server@.{service,socket}) are provided to use that
feature with systemd. They need to be instantiated with the value of feature with systemd. They need to be instantiated with the value of
$WAYLAND_DISPLAY (multiples instances can co-exists). $WAYLAND_DISPLAY (multiples instances can co-exists). The recommended
way of enabling the systemd-managed server is by running
*systemctl --user enable --now foot-server@$WAYLAND\_DISPLAY.socket*;
this way the service will only be started when needed thanks to socket
activation.
Note that starting *foot --server* as a systemd service will use Note that starting *foot --server* as a systemd service will use
the environment of the systemd user instance; thus, if you need specific the environment of the systemd user instance; thus, if you need specific

View file

@ -8,6 +8,3 @@ NonBlocking=true
Requires=%N.socket Requires=%N.socket
Description=Foot terminal server mode for WAYLAND_DISPLAY=%i Description=Foot terminal server mode for WAYLAND_DISPLAY=%i
Documentation=man:foot(1) Documentation=man:foot(1)
[Install]
WantedBy=wayland-instance@.target