Hehe, sadly I was the one who posted that. It only goes so far.
Another thought I've had is that maybe I can aggregate interfaces
separately. Unfortunately I don't have access to a maching with
cflowd at the moment, but I seem to remember being able to select
particular interfaces of interest. Maybe with the help of some Perl
code to find out all the interfaces in a data file, then to loop
around aggregating the stats for each interface in a serial fashion...
"K.C. Smith" wrote:
> I've yet to face this problem. However, I seem to recall that someone else
> posted that they worked around it by aggregating first to a smaller,
> intermediate time period and then aggregating again to their larger, final
> time period. Maybe hours, then days, for example. It certainly makes
> sense. Good luck.
> On Wed, 17 Oct 2001, Martin van den Nieuwelaar wrote:
> > Hi people,
> > To re-visit the issue of memory usage once more, it would seem that I
> > have an artsagg process that is using more than 2GB of memory and then
> > dying. This is on an Intel GNU/Linux system. I'm at a loss as to
> > what to try next. Thoughts, anyone? I don't really want to have to
> > stop gathering some of the stats (netmatrix, etc) because we're using
> > everything we gather.
> > --
> > Expert carrier network traffic analysis and visualisation
> > http://www.gadgets.co.nz/products.shtml
> > xenaphobia: The fear of being beaten to a
> > pulp by a leather-clad, New Zealand woman
> > --
> > cflowd mailing list
> > firstname.lastname@example.org
-- Expert carrier network traffic analysis and visualisation http://www.gadgets.co.nz/products.shtml xenaphobia: The fear of being beaten to a pulp by a leather-clad, New Zealand woman -- cflowd mailing list email@example.com
This archive was generated by hypermail 2b29 : Tue Oct 23 2001 - 16:17:24 PDT