I use conch connection sharing pretty extensively, and I love it. As I've been working on a laptop a lot lately, I've noticed something a little undesirable though. When I suspend long enough to disrupt my network connection, then resume, the conch process seems not to be aware that it no longer has a network connection. The ~/.conch-* unix socket remains, and any attempts to connect with conch to the host hang indefinitely. Killing the owner of the unix socket, or simply deleting the unix socket resolves the issue. Could conch be made to act a little better in this situation? Jp -- Seduced, shaggy Samson snored. She scissored short. Sorely shorn, Soon shackled slave, Samson sighed, Silently scheming, Sightlessly seeking Some savage, spectacular suicide. -- Stanislaw Lem, "Cyberiad"