On Jan 7, 2006, at 11:11 AM, Zhumabekov Yerden wrote:
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.
IMO Dave Plonka's CFlow perl module is really the correct solution to
this problem. If you take the time to write your perl well, it's
quite fast, and it's very feature rich. Robin Sommer wrote a python
module to do similar things. Both are provided in the contrib/
directory of the flow-tools distribution. The link on splintered.net
to Robin's page is stale, a currentl link is http://www.icir.org/
robin/flowtools/.
Using a web UI to generate arguments for a shell tool presents
security problems that really need to be handled (eg by enabling
Perl's Taint flag and then untainting the web data) which can be non-
trivial to implement.
-alex
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
