lib-bsd socket close issues
sebastian.huber at embedded-brains.de
Fri Apr 5 11:04:53 UTC 2019
On 05/04/2019 12:41, Matthew J Fletcher wrote:
> 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 error. The particular case is when my application
> tries to connect(), which fails as the tcp port is not open.
> The application is a reasonably complex multi task project that will
> have lots of threads using sockets at the same time, could that be
> relevant ?
> Interestingly i've also had problems with the httpd (mongoose) server
> "leaking" if web pages are opened to quickly as well, i never really
> got to the bottom of it, i just ended up at 512 sockets and hope
> people dont view pages to quickly.
You can view the status of the sockets with the "netstat -la" command.
Maybe it helps to port also the SOCKSTAT(1) command:
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the users