Re: Upcoming time boundary events

On 6/9/25 01:25, Lawrence D'Oliveiro wrote:

On Sun, 8 Jun 2025 23:39:23 +0100, chrisq wrote:
 

That's complicated in unix by the fact of multiple 'known' port
numbers for eg: ssh, telnet, nfs.etc. inetd looks at the port number
then spawns off the relevant process, depending on the port number.
Simple, neat and elegant, one of the good ideas from unix 4.3, back
in the 1980's. rBeing rplaced by xinetd, for better security.

 systemd generalizes this with its socket-based service activation
concept: a single unit definition can specify any number of each of
IPv4 and IPv6 ports, Unix-family socket names, and also named pipes,
to listen on. Oh, and other things like VSOCK and Netlink endpoints as
well. Also POSIX message queues, USB function endpoints, and some
other lesser-known features.
 <https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html>

That's interesting, but wonder if they really needed the overarching
complpexity of systemd to enable that. More productive and less
disruptive to build on what is already there, but ymmv.
Chris