How does one acquire a bunch of "orphaned" (no associated process pid)
udp connections or more importantly -- how does one get rid of them
without a reboot. The limit is around 1024 before the machine goes
squirrelly. I'm been doing a lot of dns lookups and I suspect that is
the cause.
Here's a partial "netstat -up" list.
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Progra
udp 0 0 tuxtogo:mainsoft-lm resolver1.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:1302 192.168.0.2:domain
ESTABLISHED -
udp 0 0 tuxtogo:1299 resolver2.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:4775 resolver1.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:nv-video 192.168.0.2:domain
ESTABLISHED -
udp 112 0 tuxtogo:4340 resolver2.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:4278 ns3.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:4274 resolver1.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:4269 ns1.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:3884 ns3.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:3883 resolver1.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:3881 ns1.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:3626 ns3.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:3447 resolver1.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:3417 ns1.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:rib-slm ns3.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:sah-lm resolver1.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:caps-lm ns1.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:3170 ns3.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:3138 resolver1.level3:domain
ESTABLISHED -
udp 0 0 tuxtogo:icpv2 ns1.tampabay.rr.:domain
ESTABLISHED -
udp 0 0 tuxtogo:ttc-etap-ns resolver1.level3:domain
ESTABLISHED -
TIA
Ed.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:30:21 EDT