4 ms·
`inetd` was an early attempt at avoiding every process having to write their own daemonization code.
by lgas 2y ago
`inetd` was an early attempt at avoiding every process having to write their own daemonization code.
- PaulDavisThe1st 2y agonot really. inetd was an early attempt at avoiding every process dealing with the basics of waiting on a socket for a connection, forking off some process to deal with it and managing the socket and the connection. inetd waited on "all" the sockets; when a connection came in, it started the configured application to deal with it. daemonization didn't really figure into it, AFAIR.
- erik_seaberg 2y agoI thought inetd let you conserve memory because rarely-used daemons don't need to run continually.