Thanks for the feedback, indeed I have not seen the -l flag set but my main problem still remains:
 
Starting at a bandwidth of about 2 mbit ntop terminates after a few minutes (sometimes within seconds) without any message in the log. 
 
The only way to run ntop is without any of its main features (--disbale-decoders and --disable-sessions).
 
There are nearly no packets droped, CPU is near idle (it's running on a Xeon 2,8 GHz machine) and memmory usage is at 126 MB (if running with the above flags).
 
Dropped (libpcap) 0.0% 6,931
Dropped (ntop) 0.0%

0

 
So my question here is...
 
- Is there someone else running version 3.0 on some "high bandwidth network"? What's your experience?
 
- Can someone point me to some code fragements that may be worth looking at for debugging this issue?
 
Many thanks, Marcus

"Mercer, Jeff" <[EMAIL PROTECTED]> wrote:
That's the packet capture log, which is enabled with the -l or --pcap-log parameters. It's NOT the same as the ntop log...


Gesendet von Yahoo! Mail - Jetzt mit 100MB kostenlosem Speicher
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to