On 3.3.10 rev 3780 - Solaris 10 x86. Had this same problem on 3.2 on FreeBSD...
Anyway, nTop blows up after an IDLE_PURGE cycle. There was no entry in the log this time even though I have -t 5 specified. On FreeBSD it would through a signal 11. "One" of the reasons I updated Is to hopefully solve this problem. I'll run it in gdb again and post anything I find. Anyone else having this issue? I have a lot of hosts "monitored' - like... 12,000 ish at times. Not sure if that's part of the problem or why it's more apparent for me? TIA! Gary <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
