lkml.org 
[lkml]   [1996]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Subject'Socket destroy delayed'
Date
From
Alan wrote:

>> Tell me more. I need to know these sort of things...

FWIW:

I can reliably get a "socket destroy delayed" by pinging a non-existent
host on the local network, and hitting ctrl-c after a couple of seconds.
This then shows up almost immediately in the syslog:

Apr 1 15:51:56 pcpaul kernel: Socket destroy delayed
Apr 1 15:52:06 pcpaul kernel: Socket destroy delayed

(OK, the second line takes a bit longer :-)
After this, it's over.

This is on 1.3.73. I've already patched up to 1.3.80, but I'm waiting
for some process to finish its brute-force calculation before
rebooting... It has already run for more than a week.

Paul Slootman
--
Murphy Software, Enschede, The Netherlands There is no such thing
work: paul@ahwau.ahold.nl / paul@murphy.nl as a coincidence.
home: paul@wurtel.hobby.nl


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