There are situations when xinetd starts leaking descriptors for spawned children. The problem exists since version 2.3.8 and still not fixed in xinetd-20021209. --- --- Cite from Steve Grubb: --- Here\'s a link to the e-mail that I posted to the group when I discovered the cause of the leaked descriptors: <a href="http://marc.theaimsgroup.com/?l=xinetd&m=103767881425253&w=2">http://marc.theaimsgroup.com/?l=xinetd&m=103767881425253&w=2</a> And here\'s a link to an e-mail where someone else explained what he discovered about the descriptors being mixed up: <a href="http://marc.theaimsgroup.com/?l=xinetd&m=103893604709367&w=2">http://marc.theaimsgroup.com/?l=xinetd&m=103893604709367&w=2</a> And here\'s a test script he supplied: <a href="http://marc.theaimsgroup.com/?l=xinetd&m=103893602009155&w=2">http://marc.theaimsgroup.com/?l=xinetd&m=103893602009155&w=2</a> ---
It also leaks descriptors of unclosed configuration files.
xinetd-2.3.9-alt5.20021209 no longer leaks config files.
Fixed in xinetd-2.3.9-alt6.20021209 (at least, passes my test).
merged into xinetd-2.3.10