Jivin Mike Frysinger lays it down ...
> 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 ?
No, our change log is minimal and the coder has left, but I checked
and he doesn't recall, doh.
Anyway, chances are and error logged to stderr was interrupting whatever
protocol was being run.
I don't understand why rcp/rsh would require stderr to be redirected,
but then I don't pretend to understand motivations of coders.
For reference the change has been in the dist for nearly 3 years. I know
that scp and ssh are not affected (better choices than rcp/rsh ;-) ;-)
But that doesn't help you.
If you are building a new system from scratch then my guess is you can put
it back. For us, putting it back will mean a regression. A solution
that fits may be:
#ifdef SNAPGEAR
providing no one else has been enjoying the current behaviour. I just
need to check the define on that one though,
Cheers,
Davidm
--
David McCullough, [EMAIL PROTECTED], Ph:+61 734352815
Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
