I wonder why inetd fell out of favor in the UNIX realm. Being able to write a network service using just stdin and stdout is very comfy.

Follow

@moody as I recall it didn't keep up with scale due to process launch overhead, which was quite bad on busy websites running Apache 1. Once the tuning guides said to use what became the apache pre-fork model it was the beginning of the end.

And then a few security incidents and the fact that keeping idle telnet, ftp, and finger daemons running was no longer a significant resource drain sealed the deal.

@moody Could probably do something like inetd but without that process launch penalty with FastCGI.

@pra @moody for the "simple service doing some input and output", I guess *SGI (PSGI, WSGI &c.) often fills this niche today as well.

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!