Robert Atkinson wrote: > flow-cat /nfs/flows | flow-print
> is the most simple (i think) you can get. Yes, most simple, but, I dare to doubt, not fastest. F.e., you wanna provide web-interface to flow-capture's file storage. If you combine these utils and self-made parser (Perl, Python etc.), calculation time become quite long. Besides, subtle aggregation schemes, subnets division, etc. will not boost it, too. I'm willing to create some kind of web-interface, using C and flow-tools library. Maybe, then I'll have the courage to write down some tutorial for that. Does anybody still need it? > The entire package is made to be broken down into a subset oftools, > each program being a small piece you need to extract what you want. Yeah, agreed. That's perfect for interactive work in shell. > I'm not positive, as I haven't gotten it working yet, but I think flowscan > will read the data that flow-capture saves. -- Zhumabekov Yerden _______________________________________________ Flow-tools mailing list [EMAIL PROTECTED] http://mailman.splintered.net/mailman/listinfo/flow-tools
