IETF-SSH archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: closing a channel



On Sun, Mar 24, 2002 at 09:30:36PM +0100, Niels Mller wrote:
> Markus Friedl <markus%openbsd.org@localhost> writes:
> 
> > On Fri, Mar 22, 2002 at 10:30:52PM +0100, Niels Mller wrote:
> > >   /bin/sh -c "echo foo; exec >/dev/null; exec 2>/dev/null; sleep 30; exit 17"
> > 
> > the reason for linking CHANNEL_EOF to CHANNEL_DATA only was:
> > 
> > /bin/sh -c "echo foo; exec >/dev/null; sleep 30; exec 2>/dev/null; sleep 30; exit 17"
> > 
> > so the EOF messages triggers a close(stdout) in the client
> > without waiting 30 more seconds.
> 
> I see. I don't think it's a very strong argument, though.

Sure, but applications using ssh might behave different if the EOF
is delayed (e.g. stderr is not closed at all) and not send an
EOF in the other direction.



Home | Main Index | Thread Index | Old Index