On Tue, Dec 1, 2009 at 5:24 AM, Corinna Vinschen <corinna-cyg...@cygwin.com> wrote: > > On Nov 30 11:23, Corinna Vinschen wrote: > > On Nov 26 22:42, Jeremy Hetzler wrote: > > > I have cvs on a client machine connecting to a host over ssh. The cvs > > > procedure finishes, but the connection does not terminate until I hit > > > ctrl-c. The cvs process is then left running on the host. Regular ssh > > > connections (ie interactive login) do not have this problem. > > > > > > The host machine is Cygwin 1.7.0 on Windows 7; the client is Cygwin > > > 1.5.25 on Windows XP. Attached is a cygcheck from the host and debug > > > output from sshd. > > > > > > Is there anything I can do to fix this? > > > > Dunno, yet. Is this a new problem? In other words, did this effect > > start to occur with 1.7.0-65, or do you already suffer calmly for a > > longer time?
Previously the server was 1.5.25 on XP. That worked fine (and still works fine). When I moved to Win 7 and 1.7 the problem appeared. Running 1.5.25 under Windows 7 on the server solves the problem. Whatever the problem is, it only appears under 1.7. > > I tried the same scenario, a cvs server running under Cygwin 1.7 and > a client running under Cygwin 1.5.25. I tried both socket types as > introduced with 1.7.0-65, and I can't reproduce the aforementioned > effect. http://cygwin.com/acronyms/#BLODA? > Disabling Windows Defender and Windows Firewall has no effect. I'm not running any of the other programs mentioned there. -- Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple