Package: ssh Version: 1:4.6p1-5 Severity: normal Hi,
If you are using control sockets with ssh, if your ssh session dies (or is killed) then the control socket is left in your .ssh directory. The next attempt to connect to the same host results in an error like: [EMAIL PROTECTED]:~$ ssh remote Control socket connect(/home/puck/.ssh/ssh_control_remote_22_puck): Connection refused [EMAIL PROTECTED]:~$ You then have to manually remove that file and then run ssh again. It seems to me that ssh should be smart enough to remove the file if it receives a connection refused. Cheers! -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.1-dirk (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ssh depends on: ii openssh-client 1:4.6p1-5 secure shell client, an rlogin/rsh ii openssh-server 1:4.6p1-5 secure shell server, an rshd repla ssh recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
