+ Aaron Nabil <[EMAIL PROTECTED]>:
| And that tcpserver, unlike inetd, doesn't attach stderr to the
| network connection. In fact all of the children inherit tcpserver's
| stderr! I don't see any obvious side-effect of this yet.
This is undoubtedly intentional, and quite useful. You can just pipe
the stderr of tcpserver into your favourite logging tool, and have the
spawned children log stuff that way. If you ever *need* to have the
child's stderr connected to the network socket, it is of course
trivial to arrange this.
- Harald
