On Fri, 11 Apr 2008, Jose-Marcio Martins da Cruz wrote: > I have a strange behaviour here. I'm not sure if this is a dkim or > Solaris problem (I have dkim 2.5.2 running on a T2000 box under Solaris 10). > > # netstat -an | more > > UDP: IPv4 > Local Address Remote Address State > -------------------- -------------------- ---------- > 194.214.158.200.33142 194.214.158.200.53 Connected > 194.214.158.200.62241 194.214.158.200.53 Connected > 194.214.158.200.53916 194.214.158.200.53 Connected > 194.214.158.200.42921 194.214.158.200.53 Connected > ...
I'm assuming you have _FFR_DNS_UPGRADE compiled in and are using USE_ARLIB? If not, no part of the dkim-milter package uses TCP, so those probably aren't associated with its code directly. > # lsof | grep UDP | grep dkim | head > dkim-filt 25770 root 9u IPv4 0x3001430c7c0 0t0 UDP paris:63667 > dkim-filt 25770 root 10u IPv4 0x30014308400 0t0 UDP paris:64066 > dkim-filt 25770 root 11u IPv4 0x30014309c00 0t0 UDP paris:59999 > dkim-filt 25770 root 12u IPv4 0x30014396d00 0t0 UDP paris:41292 > ... Again assuming you're using libar, it only allocates a single UDP descriptor at any given time. If it decides to change which nameserver it's using, it closes the one it has before opening another one (which isn't even strictly necessary; it's just being diligent). The same logic is applied for TCP connections. If you're not using libar, then the stock resolver is doing this for some reason. -MSK ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
