i mislead:
>flowdump is a binary executable used to debug what is arriving from the
>cflowdmux process. It attaches to the shared memory buffer
>offered by the
>cflowdmux (in the same fashion that cflowd does). It doesn't
>analyse the
>raw flow files. You'll notice perl is complaining about the content of
>flowdump - fair enough considering it's a binary :-)
flowwatch is the process i'm referring to here, not flowdump.
-- cflowd mailing list cflowd@caida.org
This archive was generated by hypermail 2b29 : Tue Jun 26 2001 - 22:24:47 PDT