inetd fd leak?

[Cathey, Jim]

>Please try 1.15.0

After back-porting the changes to the 1.13.2 environment
so that it will compile, it still exhibits the slow leakage
of socket fd's.  (The changes to 1.15.0 are mostly #definery
to compile, and putting back the non-parser_t version of the
config file logic.  I don't think this is significant to the
problem at hand.)  It's been running less than an hour, and
there are already six sockets open, up from one in the beginning.

(Our target system is expected to run for years at a time with
no problems and no reboots, and it will soon be in a noticeable
part of the cell phone infrastructure of the USA, in thousands
of field sites that nobody wants to have to drive to to
power-cycle because they can't telnet in anymore!  We're
motivated to fix this.)

Stimulus behavior is a mix of the telnet firehose I gave,
along with disabling and enabling the telnet service a
few times via commenting in and out the (lone) service
line and HUPping inetd.

I have attached the composite 1.13.2/1.15.0 inetd.c file
(as a diff -u from 1.15.0) that I'm using.

Did I say six sockets?  It's up to eight since I started
composing this message!

-- Jim




-------------- next part --------------
A non-text attachment was scrubbed...
Name: inetd.diff
Type: application/octet-stream
Size: 12769 bytes
Desc: inetd.diff
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20090903/8d8aa8f8/attachment-0001.obj>