On Sat, Mar 25, 2017 at 9:04 AM, Laurent Bercot <[email protected]> wrote: >> Unless they do want _remote user_ to see the message. >> >> For example, if you start a shell over a tcp connection >> ("poor man's telnet"), you do want to see shell error messages >> when you work in that shell, right? >> >> IOW: inetd can't know which behavior is desirable, since both make sense. >> >> So the best thing is to follow the existing established practice >> (if it exists). I googled for it and there is a somewhat weak indication >> that inetd's of various Unixes did send stderr to the socket. >> Even wikipedia says: >> "... >> inetd hooks the sockets directly to stdin, stdout and stderr >> of the spawned process" > > > Ah, wikipedia, that famous normative specification site. ;)
https://www.freebsd.org/cgi/man.cgi?query=inetd "The server program is invoked with the service socket as its standard input, output and error descriptors" Show me an implementation of inetd which does not do this. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
