Channels API and ~& question

[Nicolas Williams]

I'll answer the question I was really after:

To forcibly close the channel associated with a session call
chan_read_failed(), chan_write_failed() and chan_close_fds() on said
channel. Seems to work fine. See the feature patch I posted today.

I think a don't-hang-on-exited-but-still-open-session feature could be
coded that does the above upon receipt of the session-exit message for
the last session.

Please let me know if I'm horribly mis-understanding the channels API...

Cheers,

Nico


On Tue, Jan 15, 2002 at 03:37:38PM -0500, Nicolas Williams wrote:
> When processing ~& with SSHv2 OpenSSH sends \004 (EOT) and does not
> bother sending SSH2_MSG_CHANNEL_EOF.
> 
> Why is that?
> 
> Why is there no direct way to get SSH2_MSG_CHANNEL_EOF or
> SSH2_MSG_CHANNEL_CLOSE sent? Or is there and I'm just missing it?
> 
> Thanks,
> 
> Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.