Perhaps its time to change libzmq master back to using ephemeral ports?
On Thu, Nov 28, 2013 at 1:16 AM, KIU Shueng Chuan <[email protected]> wrote: > Some relevant threads: > > http://grokbase.com/t/zeromq/zeromq-dev/119vymt31j/zmq-occupies-random-tcp-ports-on-windows > > http://lists.zeromq.org/pipermail/zeromq-dev/2013-May/021457.html > > It seems that one person (Michal) was affected by the original use of > ephemeral ports. Others prefer to just repatch their copy to use ephemeral > ports. > > On Nov 28, 2013 7:43 AM, "Stew Scott" <[email protected]> wrote: >> >> I noticed there has been a lot of traffic about this particular function >> and the potential for handle leaks, but no one has asked why this function >> uses a fixed port instead of a dynamic port to establish the pair. I >> recently encountered a problem where port 5905 was in use, and it causes an >> exception that kills the application (on this particular machine we >> increased the dynamic port range to include 5905). >> >> >> >> Is there some reason why the port is hardcoded instead of simply using >> whatever port is available? It seems an oversight to me that I may have to >> recompile ZeroMQ to use a different port if our software is going to be >> installed on a device where that port is already taken. I notice in the >> comments of the function that it mentions using a dynamic port, but doesn’t >> actually do so. >> >> >> >> Stew Scott >> >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
