This works fine with ssh1 on the same system. I didn't expect it to
break with ssh2.
Is this a known restriction that I missed someplace? If so, it does
limit ssh2's usability as an rsh replacement.
Ric
tc lewis wrote:
>
> this has worked for you before? i thought ssh typically opened a new tty,
> and thus interfered with using pipes right from the start.
>
> -tcl.
>
> On Fri, 23 Feb 2001, Ric Anderson wrote:
>
> > On solaris 7, using ssh.com's ssh2 version 2.4.0, I consistently
> > get hangs when doing
> > ssh somehost somecommand | something that exits before ssh2
> > As a test case, I used
> > ssh somehost -n last | true
> > which never returns to a command prompt.
> >
> > It appears ssh2 completely ignores SIGPIPE, proceeds to burn
> > cpu cycles after "true" exits.
> >
> > Has anyone else seen this or is something amiss with my build?
> >
