[BusyBox] Wishlist for inetd features?

[Larry Doolittle]

Tomi wrote

> The simplest version that came into my mind is just a simple daemon
> which listens one (TCP*) port (given as numeric value in command line)

Sounds like tcpserver.  See
   http://cr.yp.to/ucspi-tcp.html
which also references other competing TCP server infrastructure
software.  I don't think we need to write one more.

I know djb's programming style; it has unmatched reliability, and
will _never_ integrate with busybox.

He has other software indexed on http://cr.yp.to/software.html.
There is one other intriguing piece of work that may be relevant
for some of this network embedded work, that is
   daemontools: a collection of tools for managing UNIX services
   http://cr.yp.to/daemontools.html

I'd love to move my desktop system over to something based on
daemontools instead of the gawdawful Red Hat SysV scripts.  The
core problem is that too many upstream daemon writers make their
programs daemon themselves internally, which breaks the core
assumption of both daemontools and init.  This action destroys
a useful piece of information, the PID of the running daemon.
Now we have that cheesy layer of scripts that tries to guess it,
instead of having init or daemontools do the job right every time.

Sorry for the tangent rant.

    - Larry