Hi all, I recently ran into an issue where a third party transferred some corrupt flow-capture files to me which caused all sorts of issues on my end.
We re-import into our application using flow-send (long story) which of course didn't mind that the values in the flows were way out of range (eg start/end years from 1970 through 2109 etc). So far, the only way I've found to check a flow file is as follows. The exit code is still zero no matter whether the file is corrupt or not which is arguably a bug but not the point of this post: # flow-cat ft-v05.2009-07-16.040000+1000 > /dev/null flow-cat: inflate(): failed # echo $? 0 Is there another better or more lower level way of testing internal corruption of flow files? While I realise I could use flow-nfilter to count/check whether start/end dates were too far away from the purported capture period this really seems like a case of looking at the symptoms rather than the cause. Cheers, Andrew _______________________________________________ Flow-tools mailing list [email protected] http://mailman.splintered.net/mailman/listinfo/flow-tools
