David Ziemba wrote: > On 7/8/08 9:58 AM, "Michael Handiboe" <[EMAIL PROTECTED]> wrote: > > I can only say positive about my experiences after switching to Linux with > PF_RING from FreeBSD 7.0-RELEASE. The only time I've had to restart nTop > was after a box reboot after OS patches or to build the latest release of > nTop. > > I firmly believe nTop is extremely robust for what I'm using it for, and > tremendously robust for it's intended use Ok, so: is there any way I can determine if the problem lies in some other place but ntop? I tried running it with --trace-level 5, but nothing useful shows. I tried --enable-debug, but doesen't seem to recognize this option (/usr/bin/ntop: unrecognized option `--enable-debug') I use kernel 2.6.24.5 (smp) with libpcap 0.9.8 on one machine and 2.6.21.5 (smp) with libpcap 0.9.7 on the other.
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
