Messages in this thread | | | Subject | reproducible 'socked destroy delayed' | Date | Thu, 11 Apr 1996 11:43:11 +0200 (MET DST) | From | (Thomas König) |
| |
I can still cause two 'socked destroy delayed' errors by pinging a nonexistent host on a local network in 1.3.86, then interrupting the ping process. The error has remained unchanged for quite a long time, and I've reported full details several times. If anybody's interested, I can send them.
Is it time to set up an automailer, which checks for this bug and sends a bug report every time I boot up a new kernel version? :-) -- Thomas Koenig, Thomas.Koenig@ciw.uni-karlsruhe.de, ig25@dkauni2.bitnet. The joy of engineering is to find a straight line on a double logarithmic diagram.
| |