Messages in this thread |  | | | Date | Tue, 02 Apr 1996 16:02:34 -0600 | | From | "Andrew C. Esh" <> | | Subject | Re: 'Socket destroy delayed' |
| |
Paul Slootman wrote: > 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
...
> 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.
This is reproducible on my 1.3.82, but I only get one syslog entry, as I did with .79.
-- Andrew C. Esh mailto:andrew_esh@cnt.com Computer Network Technology andrewes@mtn.org (finger for PGP key) 6500 Wedgwood Road 612.550.8000 (main) Maple Grove MN 55311 612.550.8229 (direct) http://www.cnt.com - CNT Inc. Home Page http://www.mtn.org/~andrewes - ACE Home Page
|  |