shimi wrote:

Maybe try to think what programs you used when this happend (Although
this is clearly a bug in sshd/ssh, and NOT in the programs. No matter
what a program does, leaving a session and proper cleanup are up to the
process that handles the session IMHO).

It's NOT a bug in sshd. Ctrl-D is simply a way to tell your shell (which is only one of the processes using the pty which sshd allocated) to exit. If there are othere processes using that pty, they're as much of a reason to keep the SSH connection alive as your shell program was -- SSH doesn't know what's a shell and what isn't. It cannot know that, by terminating a /bin/bash process, you meant to close the entire connection.


It's only by merit of the /bin/bash process being the last process to use that PTY that your connection usually closes as a result of a Ctrl-D.




=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]



Reply via email to