3 ms·
As the section at the end says, socket fds work even if the process doesn't have access to the underlying network interface that they were bound from. A good us
by Arnavion 3y ago
As the section at the end says, socket fds work even if the process doesn't have access to the underlying network interface that they were bound from. A good use of this fact is that it's okay to set `PrivateNetwork=yes` for socket-activated systemd services.
- CoolCold 3y agoWait for ppl come and start claiming you are against UNIX philosophy and systemd fanboy :))
- trasz4 3y agoSocket activated services first appeared in inetd(8) somewhere in the eighties and is as UNIX as it gets :)
- CoolCold 3y agoI'd hardly call it services, in terms of what inetd could do to keep the _service_, more like wrappers, but yeah. Systemd made it better - I run both xinetd based bash scripts for sorta network-accessible healthchecks used by haproxy later and 8000+ systemd's socket activated services, can compare apples to apples.