I recently pointed two new xaddrs towards my already busy flow collector and now my consolidated, compressed daily flow files have exceeded 2GB. Because of this flow-cat won't touch the files - it errors out with a memory allocation error.
> ls -al ftd-2004-05-17 -rw-r--r-- 1 netflow users 2141001910 May 18 01:38 ftd-2004-05-17 > flow-cat ftd-2004-05-17 | flow-stat flow-cat: mmap(): Cannot allocate memory flow-cat: ftio_init(): failed flow-stat: ftiheader_read(): Warning, short read while loading header top. flow-stat: ftiheader_read(): failed flow-stat: ftio_init(): failed > I'm running linux 2.4.20 on x86 and have been reading about adjusting the shared memory values in /proc/sys/kernel. The three parms that seem to get the most attention on the tuning related web sites are shmall, shmmax, and shmmni. The defaults on my system are... bash-2.05b# cat shmall 2097152 bash-2.05b# cat shmmax 33554432 bash-2.05b# cat shmmni 4096 bash-2.05b# I experimented with increasing shmall and shmmax (doubled both of them) but still encountered the above error. Do I need to do anything special like recompile flow-tools after modifying these parameters? Am I on the right track at all? The system itself has 512MB of memory and 2GB of swap. I don't think this is the result of a true resource constraint - more of a system specific configuration issue as flow-cat would happily work on files in the area of 1.8GB, but refuses do anything with sizes of +2GB. Any suggestions? _______________________________________________ Flow-tools mailing list [EMAIL PROTECTED] http://mailman.splintered.net/mailman/listinfo/flow-tools
