On Wed, Mar 19, 2014 at 4:35 PM, Navdeep Parhar wrote:
> On Tue, Mar 18, 2014 at 11:05:23PM -0700, Julian Elischer wrote:
>> On 3/18/14, 8:33 PM, George Neville-Neil wrote:
>> >On Mar 7, 2014, at 1:23 , hiren panchasara
>> >wrote:
>> >
>> >>I am thinking of committing following change that inclu
On Tue, Mar 18, 2014 at 11:05:23PM -0700, Julian Elischer wrote:
> On 3/18/14, 8:33 PM, George Neville-Neil wrote:
> >On Mar 7, 2014, at 1:23 , hiren panchasara
> >wrote:
> >
> >>I am thinking of committing following change that includes port number
> >>in "Listen queue overflow" messages.
> I th
On 3/18/14, 8:33 PM, George Neville-Neil wrote:
On Mar 7, 2014, at 1:23 , hiren panchasara wrote:
I am thinking of committing following change that includes port number
in "Listen queue overflow" messages.
I think it's a good idea. There is even more information available but
this is probabl
On Mar 7, 2014, at 1:23 , hiren panchasara wrote:
> I am thinking of committing following change that includes port number
> in "Listen queue overflow" messages.
>
I like it.
Best,
George
> New message would look something like:
> sonewconn: pcb 0xf8001b155760: Listen queue overflow on p
I am thinking of committing following change that includes port number
in "Listen queue overflow" messages.
New message would look something like:
sonewconn: pcb 0xf8001b155760: Listen queue overflow on port
13120: 1 already in queue awaiting acceptance (454 occurrences)
I've recently ran int
