On Wed, 22 Jul 2015 17:07:37 -0700 Cong Wang <xiyou.wangc...@gmail.com> wrote:
> For a real example, named randomly selects some port to bind() for > security concern. (It doesn't use bind(0) to let kernel to select port > because it is not random enough, kernel usually just picks the next > available.) When running named on a Mesos controlled host, named would > silently fail when it binds a port assigned to a Mesos container. I think named is trying to workaround security issues that were fixed 5 years ago in Linux. The kernel does not just pick the next available in current code. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
