New design. Celerity inetd...
Posted: Fri Sep 11, 2026 9:01 pm
The technique of running an internet application behind xinetd (or its predecessor inetd) is commonly referred to as using a super-server architecture, and the applications themselves are said to be running in inetd mode. [1, 2]
## How the Technique Works
Instead of a server application running continuously in the background as a standalone daemon, xinetd acts as a single delegate that listens on multiple network ports simultaneously. When a client request arrives, the process follows these steps: [1]
1. Port Listening: xinetd listens on the configured network port.
2. Process Spawning: Upon receiving a connection, xinetd spawns (forks) the associated application on demand.
3. Socket Hooking: xinetd hooks the network socket directly to the application's standard input (stdin), standard output (stdout), and standard error (stderr).
4. On-Demand Execution: The application handles the single request via standard I/O streams and exits immediately after completion, freeing up system memory. [1, 3, 4]
## Common Use Cases
This approach is highly efficient for lightweight or rarely used services (such as legacy telnet, ftp, or custom health-check scripts) because it conserves system resources by keeping application daemons dormant until they are explicitly needed. [4, 5, 6]
Inspired by mystic bbs.
## How the Technique Works
Instead of a server application running continuously in the background as a standalone daemon, xinetd acts as a single delegate that listens on multiple network ports simultaneously. When a client request arrives, the process follows these steps: [1]
1. Port Listening: xinetd listens on the configured network port.
2. Process Spawning: Upon receiving a connection, xinetd spawns (forks) the associated application on demand.
3. Socket Hooking: xinetd hooks the network socket directly to the application's standard input (stdin), standard output (stdout), and standard error (stderr).
4. On-Demand Execution: The application handles the single request via standard I/O streams and exits immediately after completion, freeing up system memory. [1, 3, 4]
## Common Use Cases
This approach is highly efficient for lightweight or rarely used services (such as legacy telnet, ftp, or custom health-check scripts) because it conserves system resources by keeping application daemons dormant until they are explicitly needed. [4, 5, 6]
Inspired by mystic bbs.