[Twisted-Python] Conch connection caching behavior over (laptop) suspend actions
exarkun at intarweb.us
Mon Jun 2 06:28:05 EDT 2003
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
Could conch be made to act a little better in this situation?
Seduced, shaggy Samson snored.
She scissored short. Sorely shorn,
Soon shackled slave, Samson sighed,
Some savage, spectacular suicide.
-- Stanislaw Lem, "Cyberiad"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://twistedmatrix.com/pipermail/twisted-python/attachments/20030602/d229a48c/attachment.pgp
More information about the Twisted-Python