❦ 14 juillet 2019 19:23 +01, Simon McVittie <smcv@debian.org>: > Some systemd system services are meant to start on-demand via socket > events (systemd.socket(5)), and can work via inetd on non-systemd-booted > systems. micro-httpd appears to be an example of this - I'm a bit surprised > there aren't more. Perhaps this indicates limitations in the infrastructure > around inetd services making it hard to implement "use systemd.socket(5) > under systemd or inetd otherwise"? inetd uses stdin/stdout to communicate with the daemon and have to launch one instance for each client connecting. systemd.socket pass a regular listening socket on first connection to the daemon and the daemon can then serve multiple clients. It is simple to convert an existing daemon to systemd.socket and it doesn't come with a performance impact. It can even simplify some aspects of an always-running daemon, like reloading without impacting the traffic. -- Familiarity breeds contempt -- and children. -- Mark Twain
Attachment:
signature.asc
Description: PGP signature