Package: ssh Version: 1:4.2p1-5 Severity: wishlist if I use control sockets and exit the first connection, the ssh process does not return until all other connections using the same control socket have been closed. of course, this makes sense. I wish that the master connection would either background itself when the user chooses to close the connection, or better yet: the first connection to any peer, which thus creates a control socket, should background the ssh process handling the control socket and spawn another ssh process that then uses the control socket. am i making any sense? if my suggestion is implemented, the following should not happen: lapse:~> (ssh dorian sleep 4 && echo "master returned: `date`") &; sleep 2; (ssh dorian sleep 4 && echo "second returned: `date`"); read second returned: Wed Feb 1 14:39:03 CET 2006 master returned: Wed Feb 1 14:39:03 CET 2006 instead, the second should return 2 seconds after the master. -- System Information: Debian Release: testing/unstable APT prefers stable APT policy: (700, 'stable'), (600, 'testing'), (98, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages ssh depends on: ii openssh-client 1:4.2p1-5 Secure shell client, an rlogin/rsh ii openssh-server 1:4.2p1-5 Secure shell server, an rshd repla ssh recommends no packages. -- debconf-show failed -- .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! fashions have done more harm than revolutions. -- victor hugo
Attachment:
signature.asc
Description: Digital signature (GPG/PGP)