-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew DeFaria wrote: | Robert Pendell wrote: |> I don't see this as a bug. The same behavior can be observed on a |> NetBSD machine when Putty is closed using that method or if my |> connection to the server drops. I usually have to log back in and |> check for processes that are still running from my previous session. | And you don't see this as a bug?!?
It would be if it happens consistently every time (sorry I didn't read the OP's message correctly the first time). I will add that my NetBSD observations were that it would happen occasionally where bash would not close automatically on a connection disconnect. Note that when that occurs there is usually an active tty session also going at the same time so openssh doesn't know the remote user has disconnected. The SIGHUP signal is probably generated by OpenSSH rather than PuTTY. Of course naturally I can't purposely reproduce this. The op had recently upgraded so it may be fixed upstream now. - -- Robert Pendell [EMAIL PROTECTED] "A perfect world is one of chaos." Thawte Web of Trust Notary CAcert Assurer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH+Siis1pR2j1qW+sRAk1zAJ9Cqv7e6R0kI5Wm7PpxC8Yv6ss3kwCePttn rrBWLqR4DzYo9n78KhtSbIo= =TCCK -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
