Re: Non-interactive commands

2007-09-09 Thread Rob Landley
On Sunday 09 September 2007 7:35:34 am Micha Nelissen wrote: > Rob Landley wrote: > > When "echo" exits, it closes its stdout so the ssh process gets EOF on > > stdin, and should pass that along through the network. But it has to > > wait for the other end to send all its data back before exiting.

Re: Aiee, segfault! You should probably report this as a bug to the developer

2007-09-09 Thread Matt Johnston
On Thu, Sep 06, 2007 at 03:51:04PM -0700, Jean Pierre Sainfeld wrote: > Hi, > I would be thankful if somebody could help me with this issue. > The conditions of the test are as follows: > 1) the test is done on the host or the target ( X86, ARM9 ) > respectively. It is done only on one side. >

Re: Non-interactive commands

2007-09-09 Thread Micha Nelissen
Rob Landley wrote: > When "echo" exits, it closes its stdout so the ssh process gets EOF on stdin, > and should pass that along through the network. But it has to wait for the > other end to send all its data back before exiting. Hence shutdown(). I Are you suggesting the local 'ssh' (which

Re: Non-interactive commands

2007-09-09 Thread Rob Landley
On Saturday 08 September 2007 3:35:24 pm Micha Nelissen wrote: > Hi, > > The following doesn't work: > > $ echo 'echo hello' | ssh host /bin/sh > > If host is running dropbear. OTOH, if host is running OpenSSH, I get > 'hello' echoed back to me. This sounds like a manifestation of using close() in