Syslog output to start. Try starting nTop with -t 5 or 6 and -K. If syslog has no benefits you'll have to run in the debugger to capture the crash in more detail.
G -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Buff Sent: Friday, June 13, 2008 1:34 PM To: [email protected] Subject: Re: [Ntop] Machine capabilities On Fri, Jun 13, 2008 at 11:25 AM, Gary Gatten <[EMAIL PROTECTED]> wrote: > That config should keep up with 20Mb/s no problem, even if it was 100% > 64Byte packets. The type of NIC, quality of drivers, etc. are key to > packet capture performance. As to what actually caused your crash - you > didn't post any info relative to that. Heh. That would probably be because I don't have a good understanding of what would be relevant. Any thoughts on that? Kurt _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop <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
