3 ms·
Eh, that's the original idea of the Unix shell, sure. But Unix has many ideas. Long running daemons have been a part of Unix systems since the beginning.
by dannypgh 8y ago
Eh, that's the original idea of the Unix shell, sure. But Unix has many ideas. Long running daemons have been a part of Unix systems since the beginning.
- tannhaeuser 8y agoBSD 4.3 introduced inetd along with TCP/IP to mainstream Unix. Quoting from [1]: > When a TCP packet or UDP packet arrives with a particular destination port number, inetd launches the appropriate server program to handle the connection. For services that are not expected to run with high loads, this method uses memory more efficiently, since the specific servers run only when needed. Furthermore, no network code is required in the service-specific programs, as inetd hooks the sockets directly to stdin, stdout and stderr of the spawned process. [1]: https://en.wikipedia.org/wiki/Inetd https://en.wikipedia.org/wiki/Inetd
- dannypgh 8y agoI'm familiar with inetd, but I don't understand your point. Unix is more than a dozen years older than 4.3BSD. Claiming that long lived daemons is somehow anti-Unix is absurd. Just ask init or getty.
- tannhaeuser 8y agoMy point was that the idea of small, self-contained apps that do one thing, and do it well, was in no way limited to shell programming. Init and getty are small, self-contained system demons that are part of the O/S rather than application servers inviting long-running, single address-space processes for business logic.