From e2d67af8ed61f1203691b64a29ccaa6d26509799 Mon Sep 17 00:00:00 2001 From: Andrea Pappacoda Date: Fri, 28 Oct 2022 21:37:20 +0200 Subject: [PATCH] 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 --- doc/foot.1.scd | 6 +++++- foot-server@.service.in | 3 --- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/foot.1.scd b/doc/foot.1.scd index afb8faf5..9b752750 100644 --- a/doc/foot.1.scd +++ b/doc/foot.1.scd @@ -123,7 +123,11 @@ the foot command line Two systemd units (foot-server@.{service,socket}) are provided to use that 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 the environment of the systemd user instance; thus, if you need specific diff --git a/foot-server@.service.in b/foot-server@.service.in index c40bb454..6fcbab6b 100644 --- a/foot-server@.service.in +++ b/foot-server@.service.in @@ -8,6 +8,3 @@ NonBlocking=true Requires=%N.socket Description=Foot terminal server mode for WAYLAND_DISPLAY=%i Documentation=man:foot(1) - -[Install] -WantedBy=wayland-instance@.target