> On 23 Mar 2017, at 5:51 PM, Dirk Lohse <[email protected]> wrote:
>
> A workaround for me is to not use inetd mode. But the reason for this
> behavior should be found and fixed - I think.
>
> Dirk
>
See networking/inetd.c:
/* manpages of inetd I managed to find either say
* that stderr is also redirected to the network,
* or do not talk about redirection at all (!) */
if (!sep->se_wait) /* only for usual "tcp nowait" */
xdup2(STDIN_FILENO, STDERR_FILENO);
inetd is tying stdout and stderr together.
Personally I think this is wrong since it generally means that
inetd services must be careful never to write to stderr.
Cheers,
Steve
--
Embedded Systems Specialists - http://workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au P: +61 434 921 300
E: [email protected]
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
