|
Sorry Rafael – look at the question
closely: “What WAS the –S option?”. It’s no longer
available. Q1(a). Can I store data in a SQL
database? Q1(b). When ntop stops I lose all my
data. Why? Q1(c). Why doesn't the -S option
work? A. ntop used to optionally store some
data in a SQL database. The code was broken, difficult to maintain, etc. and
was removed. A LONG TIME AGO. If you are reading about this in 'some'
documentation - update. Current
ntop is 3.2, which is the only version we support. There are
scripts that various users have offered to take the data dump and insert it
into a SQL database. Search the back traffic on the mailing list for them. Yes, ntop
uses memory based structures to hold usage data and they are lost when you
reset or restart ntop. Persistent
storage is in the RRD databases - there's a paper @ SourceForge that explains
them. There was
another option for some persistence - it was -S - look in FAQarchive for an
article about it, "What was the -S option?". From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rafael Barbosa Guess I found it: Q. What was the -S option? A. The -S option was the --store-mode
option, or the "Persistent storage mode" Ntop's internal structures
are basically an array of devices (network interfaces), which contains an array
of hosts (specific machines seen on the device. So
device[0] is the 1st network interface, and device[2] the third.
device[0].host[0] would be, say, the local file server and device[0].host[1]
would be a simple host. device[1].host[1] is a completely different set of
counts from device[0].host[1]. The -S
options tells ntop to store information about a specific host in a database
from run to run (-S 0 none, -S 1 all and -S 2 only local hosts). This is
only the count information about the host and does not store the information
about a device (a network interface). Further, items of dynamically allocated
storage (the devices name) are not stored. Data is
retrieved on a subsequent run ONLY when traffic is seen from that host after
the restart. (I suppose you could script a ping to each host you care about and
force the reload that way, but it hasn't been tested...) So if you
go into the host details (e.g. the 192.168.1.1.html page) you should see
prior-run information. But if
you're looking for device throughput to be preserved... nope... Also,
ntop stores the information during 1) reset and 2) shutdown. So if ntop
crashes, the persistent data will be lost. This
option was removed from ntop in the 2.1.52 development version.
On 5/29/06, Rafael
Barbosa <[EMAIL PROTECTED]
> wrote: Hello again,
|
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
