Hi Brent, Good to see progress.
The entries stay "forever", there is not an aging-out mechanism. Reason being you are supposed to do it yourself, at regular intervals, to build a time reference for the counters. For example a simplistic scenario is a cronjob entry, set up every 5 minutes, that launches a "pmacct -s -e > counters-<time>.txt". Such commandline a) fetches the whole content of the table, b) writes it to a file and c) cleans the full table up. Should be all you need to feed such data into 3rd party applications for reporting, graphing, etc. Cheers, Paolo On Thu, Mar 11, 2010 at 02:00:27PM -0800, Brent Van Dussen wrote: > Good news, no longer getting the errors and my system hasn't fallen on > its face yet. > > Also have 2-3x more entries in the memory tables so that's excellent as > well. > > My next question is regarding aging of entries in the memory table, how > is this done? At first I checked one of the tables and there were over > 100k entries, 3 or 4 seconds later when I checked the table it was down > to 50k entries and seems to fluctuate +/- 15k entries. > > I've read the INTERNALS document pertaining to memory tables but it > wasn't quite clear in this regard. > > Thanks! > -Brent _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
