On 05/04/2019 14:40, Matthew J Fletcher wrote:
Hi Peter,
I dont think netstat can do that. It just shows in the closed state as
it cannot connect (on purpose).
The netstat command can should you if TCP sockets are in the TIME_WAIT
state.
--
Sebastian Huber, embedded brains GmbH
Address :
Hi Peter,
I dont think netstat can do that. It just shows in the closed state as it
cannot connect (on purpose).
On Fri, 5 Apr 2019 at 12:35, Peter Dufault wrote:
> A basic question you probably checked: Are your sockets in TIME_WAIT state?
>
> On Apr 5, 2019, at 07:04 , Sebastian Huber <
> s
A basic question you probably checked: Are your sockets in TIME_WAIT state?
> On Apr 5, 2019, at 07:04 , Sebastian Huber
> wrote:
>
> On 05/04/2019 12:41, Matthew J Fletcher wrote:
>> Hi,
>>
>> I've not been able to reproduce either in a simple test case yet, which
>> would lead to the obviou
On 05/04/2019 12:41, Matthew J Fletcher wrote:
Hi,
I've not been able to reproduce either in a simple test case yet,
which would lead to the obvious conclusion that there is some fault in
my application. However, from my diagnostics i can see that a) all
opened socket FD's are being passed to
Hi,
I've not been able to reproduce either in a simple test case yet, which
would lead to the obvious conclusion that there is some fault in my
application. However, from my diagnostics i can see that a) all opened
socket FD's are being passed to close() and b) that close() is not
returning an err
