Hey Alistair! I think this line in your example should be changed ;)
> % flow-cat -m 1000 >> test1 ...to > % flow-gen -n 1000 >> test1 ...but I get what you mean, and I think your diagnosis is a thorough proof of the behavior I described. It's not the fault of flow-tools, but rather something that I think should be described somewhere, since the '>' shell operator is used in examples rather often, but '>>' should be avoided!! > The only way I know to get around this is to create one output file per > filter and then use flow-cat to collate them into a single file. Yes, that's a good solution. Now I just need to recompile since the Debian maintainers apparently left out support for large files. Does anybody know why they'd do that? Is there some catch here? Should I rather split filtered flows into a lot of small files because of performance? For me it makes perfect sense to just store everything in one file, since I need it all at once... Benjamin _______________________________________________ Flow-tools mailing list [EMAIL PROTECTED] http://mailman.splintered.net/mailman/listinfo/flow-tools
