Date: Tue, 2 Dec 2014 12:49:35 +0530 From: Someone Somewhere <somewheresomeoneis@gmail.com> To: Yuri <yuri@rawbw.com> Cc: freebsd-net@freebsd.org Subject: Re: Can multiple apps listen for TCP on the same port? Message-ID: <CAMW5Toax8RdrTnWe7zb2AFjdSvwc0s1Au3UAPqxowe1ssJgmhg@mail.gmail.com> In-Reply-To: <547D5493.3020407@rawbw.com> References: <547C5DD3.90604@rawbw.com> <547D1DC6.8030408@rawbw.com> <CAMW5ToZi9QCFPnF%2BdwjLCyU_OTbZjZTJaDtRGaQ=hDR7tUAP1g@mail.gmail.com> <547D5493.3020407@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
backlog is more than one since nc can wait for multiple connections via -k option(and also because backlog value is hard coded). https://www.freebsd.org/cgi/man.cgi?query=nc&apropos=0&sektion=0&manpath=FreeBSD+10.1-RELEASE&arch=default&format=html On 2 December 2014 at 11:26, Yuri <yuri@rawbw.com> wrote: > On 12/01/2014 20:22, Someone Somewhere wrote: > >> I think backlog value has no direct implication here. >> What matters is if the listening socket has been closed after accepting >> the >> client connection or not. >> -Kunal. >> > > I think backlog >1 in one-user one-connect app (as nc) might catch other > connections and later drop them. I might be wrong. > > Yuri >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMW5Toax8RdrTnWe7zb2AFjdSvwc0s1Au3UAPqxowe1ssJgmhg>