[uClibc]Re: file descriptor (socket) leakage
Erik Andersen
andersen at codepoet.org
Mon Jun 2 08:08:23 UTC 2003
On Fri May 30, 2003 at 10:03:20AM +0200, Tomislav Sajdl wrote:
>
> > But then, based on your earlier bug report, that means that
> > calling syslog() a zillion times is opening a zillion sockets and
> > thereby leaving a zillion file descriptors open, right? I took a
> > quick look at uClibc's syslog.c and I do not see how that could
> > happen though.
> >
> > -Erik
>
>
> This application simulates what freeswan does (our software had problems only
> with WARNINGs, so have that in mind), and I see that _there is_ leakage.
Ahh yes, ok. I do recall that problem now. It was fixed a
couple of months ago, but after uClibc 0.9.19 was released.
----------------------------
revision 1.11
date: 2003/04/19 23:35:01; author: andersen; state: Exp;
lines: +38 -32
Patch from Marshall M. Midden:
It turns out that uClibc's syslog.c does not close sockets when
doing retries and when it exits due to errors. This patch fixes
it.
----------------------------
I guess you will need to use a newer uClibc snapshot to address
this failure...
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
More information about the uClibc
mailing list