>>EIP: 13fe26 <get__netinfo+14e/2ac>
Trace: 14bfc8 <raw_rcv+e4/f4>
Trace: 13ffa5 <tcp_get_info+21/28>
Trace: 169081 <proc_readnet+ad/144>
Trace: 1225e6 <sys_read+8a/b0>
Trace: 10a585 <system_call+55/80>
Code: 13fe26 <get__netinfo+14e/2ac> movl 0x4(%eax),%eax
Code: 13fe29 <get__netinfo+151/2ac> movl %eax,0x14(%esp,1)
Code: 13fe2d <get__netinfo+155/2ac> movl 0x14(%esp,1),%edx
Code: 13fe31 <get__netinfo+159/2ac> pushl %edx
Code: 13fe32 <get__netinfo+15a/2ac> xorl %eax,%eax
Code: 13fe34 <get__netinfo+15c/2ac> testl %esi,%esi
Code: 13fe36 <get__netinfo+15e/2ac> je 13fe3e <get__netinfo+166/2ac>
Code: 13fe38 <get__netinfo+160/2ac> movl 0x90909000(%ebx),%eax
The only really new part is that the offending process was netstat rather
than in.identd this time. The system has been up about 1.5 months, and
ran fine for the first 30 days. Since then, it seems to be doing this
every few days, sometimes several times a day. Has anyone tracked it
down? There was a message from Alan about 2 weeks ago saying it was a
known bug and "mostly harmless".
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
________Finger jlewis@inorganic5.fdt.net for PGP public key_______