The docs/FAQ file consists of over 100 pages - carefully written to answer most of the questions routinely asked on this list - and in nested levels of detail so you don't have to read 100s of lines you don't care about.
If you had looked for the old -S option you found in the old docs, you would see: "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." If you had searched for mySQL: "Q. But what about SQL and mySQL A. Removed in 2.1.50+ versions - use rrd" Followed by: "Q. But I really, really, need the data in an sql database. A. If you are only interested in saving your netflow data in MySQL, use the script ntop/NetFlow/netFlowClient.pl (netflow v5). With few additional lines you could save your data in flat files, forward the netflow data or whatever. What this script does it set itself up as a netflow collector and sql inserter. The main loop just accepts a netflow packet and inserts the flow(s) into sql. To use this with a single instance of ntop, just set ntop up as a netflow sender, directed at the script (e.g. 127.0.0.1 on any port you like). Configure the script with the port # and run it. The same idea would work with sFlow, you would just have to change the packet decoding part of the script." Google for mySQL in the back traffic - mySQL site:listgateway.unipi.it - you'll see how often this is asked. If you had looked at SourceForge you would find the rrd paper. Also in the back traffic are scripts that other users have written which might do some of what you want. Don't think the answer in docs/FAQ is sufficient? Then get off of your (collective) lazy b**ts and send me some more words to include. -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Andrew Davis > Sent: Tuesday, July 27, 2004 10:30 AM > To: Burton M. Strauss III > Cc: [EMAIL PROTECTED] > Subject: Re: [Ntop] A couple a basic NTOP questions > > > You know, I can't count the number of lists where people reply with > "read the docs". Funny, cause I always read them (if I can find them) > before I post to a list. It was only *after* searching all over ntop.org > and via google that I found some very dated (ver 2.x) info, but was able > to get ntop up and running. What I was wondering about was storing the > data... why it appeared to be lost after a reboot and if storing it in > mysql was the only option. Of course, typical to most lists, no one can > just "say, you can configure it to store the data, but you need mysql" > or "no, you can't... a mysql db is the only". Had I received an answer > like that, I could move on and know what direction to go. Instead, I'm > told to read the docs (which I already have... those I could find > anyway), that the docs are old and outdated (???), and to search the > archives (which I have, but if any of you notice, when you go the page > with the archives, there's no search option and heck if I want to > download all the files, unpack them all, and then search them all). I > wasn't asking for my hand to be held. I was asking a general question so > I know which path to go down as I move forward, but as with most lists I > got the typical RTFM, though in this case, with a follow-up that says, > "oh, and TFM is out-dated". > > AD > > Burton M. Strauss III wrote: > > > Read the discussion in docs/FAQ on this topic and look over the > back traffic > > on this list. Heck, the same question was asked within the > last 48 hours. > > > > Oh, and be sure to read the CURRENT docs, not some old crud you found on > > www.ntop.org. > > > > -----Burton > > > > > >>-----Original Message----- > >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > >>Andrew Davis > >>Sent: Monday, July 26, 2004 6:47 PM > >>To: [EMAIL PROTECTED] > >>Subject: [Ntop] A couple a basic NTOP questions > >> > >> > >>I have NTOP installed and seemingly working just fine. I found a generic > >>"how-to" a bit difficult to find... at least for any current Linux > >>distro's, but nonetheless, I think I have it working. > >> > >>My main question is regarding keeping data after a reboot. It *appears* > >>that once I reboot the server running NTOP and restart NTOP, the > >>previously collected data is lost. Is there a simple way of storing it? > >>I noticed in a doc somewhere that its *possible* to store it in a mysql > >>DB. Is this the only choice? Are there any instructions on setting this > >>up? I'm very interested in trending over time, but the server NTOP runs > >>on will need to be rebooted on occasion. > >> > >>Thanks in advance, > >>-- > >> Andrew Davis > >> North County Computers > >> http://www.nccomp.com > >> > >> Email: [EMAIL PROTECTED] > >> Local: 760-525-4689 > >> Toll Free: 877-735-4689 > >> > >> <a href="http://www.nccomp.com";>North County Computers</a> > >> > >>_______________________________________________ > >>Ntop mailing list > >>[EMAIL PROTECTED] > >>http://listgateway.unipi.it/mailman/listinfo/ntop > > > > > > > > -- > Andrew Davis > North County Computers > http://www.nccomp.com > > Email: [EMAIL PROTECTED] > Local: 760-525-4689 > Toll Free: 877-735-4689 > > <a href="http://www.nccomp.com";>North County Computers</a> > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
