Socket destroy delayed

Daniel Schepler (daniel@shep13.wustl.edu)
Mon, 1 Apr 1996 20:33:22 -0600


I was running Linux 1.3.81 when this happened -- the message

Socket destroy delayed (r=0 w=236)

was repeated once every ten seconds. At the time, I was doing a
traceroute which hung, and when I ^C'd it, the message started. Then,
after I rebooted and the box had been up just a couple hours, I was
logged in remotely, so I have no idea what I did to get the message

Socket destroy delayed (r=0 w=1608)

which was only printed once. BTW, I had been playing around with
tcpdump in both cases; this is also what I was doing when 1.3.57
crashed after almost 67 days. I've also had a couple complete lockups
(unpingable) since then, but I was running X, so I couldn't see
whether there were any panic messages or not.

(System is 486, 3c509 card, 20M memory, nothing like masquerading or
firewalling enabled.)