Your message to ntop or ntop-dev has been seen.
However, you have:
* neglected to provide important information
- using the built-in problem report form is STRONGLY suggested.
* appear not to have taken advantage of existing information
or
* haven't taken other steps we ask you to do when posting to the
mailing list
Hence this semi-automated response.
Posting guidelines are in the docs/FAQ file in the source tree, and
(although perhaps not the latest copy) in the "HOWTO ask for help"
item at http://snapshot.ntop.org and at http://www.ntopsupport.com
in the documentation section.
1. ONE and only ONE problem / issue / question per message.
With a meaningful subject.
The goal is that if you're asking a common question, the
subject would have allowed you to find it in the back
traffic for the mailing list.
2. Search the back traffic on these lists. There is a searchable archive
at http://search.gmane.org
3. Read the docs/FAQ file in the source. You should get a recent version,
not one
from some old source .tgz. As a last resort, a HTMLed version is posted
in the
documentation section of http://www.ntopsupport.com.
4. Check snapshot, http://snapshot.ntop.org - this is a community FAQ
collection.
Entries from snapshot are migrated into docs/FAQ fairly routinely, but
the
newest stuff (and some oldies but goodies) are at snapshot.
5. We support only the current versions of ntop. This is either:
* the last release, v2.2.
* the cvs (and tell us the last time you did a checkout)
or
* the latest development version posted at SourceForge
(if there is one posted)
If you use a port/package and the latest version available for your
OS is some release candidate from a year ago, sorry. Contact the
packager and ask them to get current.
6. Post the information about your environment we ask for.
We STRONGLY suggest you use the automatically generated "Problem Report"
form that since it contains much of the necessary information.
7. Make sure you're in a supported environment (./configure --showoses).
If it's an unsupported environment, we're interested in your efforts to
make ntop work, but we don't have the time, resources, knowledge and/or
insterest to do it ourselves.
8. For software 'crashes', please run ntop under the gdb debugger and
capture
the full failure information. Brief instructions on using gdb are in the
docs/FAQ file.
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of WIm
Bakker
Sent: Thursday, July 31, 2003 9:13 AM
To: [EMAIL PROTECTED]
Subject: [Ntop] Newbie questions about ntop
Hai,
Slackware 8.1
ntop-2.2c
problems:
-b option causes ntop to bail out immediately, is this a bug?
either of the -g , -n or -s options cause the webinterface of ntop
to stop functioning after a short time, notably after viewing the matrix
page,
so
commandline used thus:
/usr/local/bin/ntop -M -d -u 2000 -P /usr/local/etc/data/ -m
172.16.128.0/24,10.0.0.0/255.0.0.0 -i eth1,eth0
after some time no updates are being seen in the webinterface anymore
as if there is no more traffic for the various hosts.
The networkload graph doesn't fill up but shows only a few minutes of
networktraffic (I assume as it states "last 60
minutes average throughput" that there should be something of a continuing
graph) in allways the same kind of peak showing the past 1-2 minutes.
Any hints would be welcome
TIA
Wim Bakker
--
UnetIX Linux Solutions BV
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
