Hmm. Which resolver is it using? Does strace show anything useful (try strace -eopen,socket iftop)? Can you use lsof or similar to identify files the process has open?
Hi Chris,
Thanks for the prompt reply. :)
Judging from the make output of the port it is using the forking resolver:
checking how to call gethostbyaddr_r... no idea; dropping back to the
forking resolver
I just tried to build strace onto my system, but it is having problems, I will get back to you on that one.
lsof provides interesting output:
There are the normal open files, but the interesting lines (current 174... Opps, make that 176 lines of them) are similar to:
iftop 21553 21552 root 6u KQUEUE 0xc2a08300 count=0, state=0 iftop 21553 21552 root 8u KQUEUE 0xc2987900 count=0, state=0 iftop 21554 21552 root 8u KQUEUE 0xc29e9300 count=0, state=0 iftop 21554 21552 root 9u KQUEUE 0xc2a06400 count=0, state=0 iftop 21553 21552 root 10u KQUEUE 0xc29ee600 count=0, state=0 iftop 21553 21552 root 11u KQUEUE 0xc2a11200 count=0, state=0 iftop 21554 21552 root 11u KQUEUE 0xc2b38400 count=0, state=0 iftop 21553 21552 root 12u KQUEUE 0xc29a1700 count=0, state=0 iftop 21554 21552 root 12u KQUEUE 0xc29e9d00 count=0, state=0
I tied disabling name resolving (using -n) to see if that makes a difference, and it did.
Only 18 open files, and not growing.
Do you still wish to have the strace output? I will attempt to get it running.
Cheers, Stuart Whelan Technical Lead Simulation Hardware LTD
DDI: +64 3 3778866 Mobile: +64 27 2828074
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.535 / Virus Database: 330 - Release Date: 1/11/2003