~mdw / sgt / putty / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3e64ff6) | patch
Ben Hutchings reports that new PuTTY instances created from the saved
authorjacob <jacob@cda61777-01e9-0310-a592-d414129be87e>
Tue, 8 Mar 2005 23:06:15 +0000 (23:06 +0000)
committerjacob <jacob@cda61777-01e9-0310-a592-d414129be87e>
Tue, 8 Mar 2005 23:06:15 +0000 (23:06 +0000)
commit8e90e4c629df76a23b79e19814dbbcaef448ad07
treef3329fcb1cec525d6ddd8a0ef68ec5ecb4279130tree | snapshot (tar.gz zip)
parent3e64ff651d32ecd89237218e8c26c8d064c73b31commit | diff
Ben Hutchings reports that new PuTTY instances created from the saved
sessions menu (etc) can inherit listening sockets, and that this sometimes
causes trouble. Can't reproduce any problems myself, but let's only allow
inheritance when absolutely necessary -- Duplicate Session -- in which
case there's already going to be trouble with two processes trying to
listen on the same port.

git-svn-id: svn://svn.tartarus.org/sgt/putty@5468 cda61777-01e9-0310-a592-d414129be87e
windows/window.c diff | blob | blame | history
Simon Tatham's PuTTY GUI SSH client; import of svn://svn.tartarus.org/sgt/putty