| > Another is zero cost for a rarely used tool. Zero cost is only true for unused services. For rarely used services, it's a rarely occuring full cost that might come by surprise at a bad time. > I think a nice benefit for an administrative tool is the ability to update it, and reload the updated version. This is only a benefit if the systemd socket unit is co figured to operate in inetd-mode (Accept=yes), where systemd spawns a new process for every accepted connection, which is quite inefficient resource-wise. "Normal" systemd socket activation just starts the service and hands over the socket. The service runs indefinitely afterwards as if it was a normal service, and needs to be manually restarted or hot-reloaded after upgrade or configuration change. > The reason why inetd didn't stick is because it's a pain to use -- it's separated from SysV init, so it needs to be very intentionally set up. Being separated has a lot of benefits - easy nesting, easy reuse in minimal containers, etc. The integrated model works best for monolithic servers. |