> Maybe all we need is to only make stdin and stdout
> non-blocking for ssh and not rsh. The trouble is that it is hard to
> reliably tell what transport you're using because people can call programs
> whatever they want.
True, relying on --rsh=COMMAND looks rather ugly and not generic.
I have no real good suggestion on how to solve this little mystery
apart maybe from adding (non)blocking for stdin and stdout as
parameters (which, in its own turn, would potentially need an ever
growing matrix of documentation)
--
Greetings,
-- Cisco Systems RP Team TAC Brussels --
Marc Duponcheel email: [EMAIL PROTECTED]
tel: +32 2 704 52 40 cell: +32 478 68 10 91
