Paul> Alan wrote:
>>> Tell me more. I need to know these sort of things...
Paul> FWIW:
Paul> I can reliably get a "socket destroy delayed" by pinging a non-existent
Paul> host on the local network, and hitting ctrl-c after a couple of seconds.
Paul> This then shows up almost immediately in the syslog:
I can duplicate this, but the messages don't persist making it a
non-problem right?
Apr 1 23:59:43 geordi kernel: Socket destroy delayed (r=0 w=536)
Apr 1 23:59:53 geordi kernel: Socket destroy delayed (r=0 w=536)
Apr 1 23:59:56 geordi kernel: Socket destroy delayed (r=0 w=1608)
[Messages stop here]
I did get a persistent socket destroy delayed by performing a manual
set of nfs mounts (a shell script with a bunch of NFS mount commands
in it) shortly after boot. This is non-repeatable though.
Apr 1 20:28:24 geordi kernel: double lock on device queue!
Apr 1 20:28:24 geordi kernel: Socket destroy delayed (r=0 w=236)
Apr 1 20:29:04 geordi last message repeated 4 times
Apr 1 20:30:14 geordi last message repeated 7 times
Apr 1 20:31:14 geordi last message repeated 6 times
Apr 1 20:31:44 geordi last message repeated 3 times
This machine is running 1.3.81 with a single 3c509 ethernet card.
Regards,
-- steve@miranova.com baur Unsolicited commercial e-mail will be proofread for $250/hour. Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone except you in November.