[uClinux-dev] #if 0 in inetd start_child()
David McCullough
David_Mccullough at securecomputing.com
Wed May 30 19:39:37 EDT 2007
Jivin John Williams lays it down ...
> Hi Mike,
>
> Mike Frysinger wrote:
> >the latest inetd does not seem to work for me with rcp/rsh ... if i change
> >the '#if 0' to '#if 1' in start_child() (the stderr/stdout redirection),
> >things work
> >
> >any idea the history behind this block of code ?
>
> We found and reported the same thing last July. I haven't done enough
> testing to know if fixing this for rsh breaks inetd for anything else,
> so we haven't committed it internally yet either.
It went in around the time of the switch to fnord, so it is possible
related to that in some way.
I am still surprised that rcp/rsh require both stdout and stderr to be
joined somehow.
Cheers,
Davidm
--
David McCullough, david_mccullough at securecomputing.com, Ph:+61 734352815
Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com
More information about the uClinux-dev
mailing list