lkml.org 
[lkml]   [1996]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 'Socket destroy delayed'/raw socket
Date
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


\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.038 / U:1.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site