Messages in this thread | | | From | Ricky Beam <> | Subject | Re: 'Socket destroy delayed'/raw socket | Date | Fri, 29 Mar 1996 11:04:18 -0500 (EST) |
| |
Letting the chips far where they may, I quote Thomas Koenig: >This is for 1.3.80. >... >Socket destroy delayed (r=0 w=268) >...
I'm still running 1.3.71 and have it set to return the source/dest addresses for that socket as well as "num" (what ever that is.)
So far, I've only had it spitting out messages once -- I restarted named. The src/dest addrs == 0, num == 53, wmem_alloc == 268 (interesting number!) I've noticed strange behavior out of raw sockets for a long time -- i.e. they never go away -- but it's never bothered me so...
--Ricky
| |