foot/foot-server@.service.in

[Service]
ExecStart=@bindir@/foot --server=3
Environment=WAYLAND_DISPLAY=%i
UnsetEnvironment=LISTEN_PID LISTEN_FDS LISTEN_FDNAMES
NonBlocking=true

[Unit]
Requires=%N.socket
Description=Foot terminal server mode for WAYLAND_DISPLAY=%i
Documentation=man:foot(1)

[Install]
WantedBy=wayland-instance@.target
Adding systemd unit files for socket activation - Support for multiples concurrent instances, templated on WAYLAND_DISPLAY - Use standard input for the socket file descriptor (inetd style) - Always use the socket provided by systemd with the systemd user service - wayland-instance@.target is intended to be a special target a bit like graphical-session.target. 2022-01-15 17:25:59 +01:00			`[Service]`
server: Use "normal" socket activation, not inetd Systemd, when doing socket activation, pass file descriptors in a non-stable order when there is multiples ones. But we only use one, so we don't need to identify it, and the file descriptors always start at 3. So use 3 for the systemd service. Source : sd_listen_fds (systemd man pages) We also need to unset variables systemd pass to socket activated process, since we don't need them and sub-process (footclient and theirs forks) could be confused by those. Closes #1107 2022-07-29 20:12:47 +02:00			`ExecStart=@bindir@/foot --server=3`
Adding systemd unit files for socket activation - Support for multiples concurrent instances, templated on WAYLAND_DISPLAY - Use standard input for the socket file descriptor (inetd style) - Always use the socket provided by systemd with the systemd user service - wayland-instance@.target is intended to be a special target a bit like graphical-session.target. 2022-01-15 17:25:59 +01:00			`Environment=WAYLAND_DISPLAY=%i`
server: Use "normal" socket activation, not inetd Systemd, when doing socket activation, pass file descriptors in a non-stable order when there is multiples ones. But we only use one, so we don't need to identify it, and the file descriptors always start at 3. So use 3 for the systemd service. Source : sd_listen_fds (systemd man pages) We also need to unset variables systemd pass to socket activated process, since we don't need them and sub-process (footclient and theirs forks) could be confused by those. Closes #1107 2022-07-29 20:12:47 +02:00			`UnsetEnvironment=LISTEN_PID LISTEN_FDS LISTEN_FDNAMES`
Adding systemd unit files for socket activation - Support for multiples concurrent instances, templated on WAYLAND_DISPLAY - Use standard input for the socket file descriptor (inetd style) - Always use the socket provided by systemd with the systemd user service - wayland-instance@.target is intended to be a special target a bit like graphical-session.target. 2022-01-15 17:25:59 +01:00			`NonBlocking=true`

			`[Unit]`
			`Requires=%N.socket`
			`Description=Foot terminal server mode for WAYLAND_DISPLAY=%i`
			`Documentation=man:foot(1)`

			`[Install]`
			`WantedBy=wayland-instance@.target`