remarkable_printer/printer.socket

[Unit]
Description=Socket for native printing to reMarkable
After=multi-user.target

[Socket]
ListenStream=0.0.0.0:9100

[Install]
WantedBy=sockets.target
socket-activate printer Previous to this commit, the printer needs to continuously run in the background, even if it doesn't do much most of the time, to keep the socket open and handle incoming connections. This commit hands over handling the open socket to systemd and the printer-code gets started by systemd only when there is something incoming on the socket. The printer itself then takes over the socket from systemd, handles the incoming data and exits afterwards, returning socket management to systemd again. This reduces running processes as well as the memory footprint of the running system. 2020-12-27 09:34:58 -05:00			`[Unit]`
			`Description=Socket for native printing to reMarkable`
			`After=multi-user.target`

			`[Socket]`
listen on 0.0.0.0 2024-03-17 22:01:00 -04:00			`ListenStream=0.0.0.0:9100`
socket-activate printer Previous to this commit, the printer needs to continuously run in the background, even if it doesn't do much most of the time, to keep the socket open and handle incoming connections. This commit hands over handling the open socket to systemd and the printer-code gets started by systemd only when there is something incoming on the socket. The printer itself then takes over the socket from systemd, handles the incoming data and exits afterwards, returning socket management to systemd again. This reduces running processes as well as the memory footprint of the running system. 2020-12-27 09:34:58 -05:00
			`[Install]`
fix potential boot issue from systemd cyclic dependency 2024-07-23 16:34:08 -04:00			`WantedBy=sockets.target`