On May 18, "To [EMAIL PROTECTED]" wrote: [snip]
For future google searching, I transcribe this off-list conversation regarding mmap and freebsd (thank you [EMAIL PROTECTED]): > > > Have a look at the -m option for flow-cat to disable mmap. That fixes > > > this problem for me on freebsd...but it's possible it's a freebsd > > > specific issues. > > is it possible you're hitting the vm.max_proc_mmap restriction? > Yes :) > Is there anything I need to consider before I set this variable to > 2147483648 (2G)? :) just set it to zero.. it disables the check. it's mostly so that threads and rfork() and such don't steal vm resources and send a machine spiraling. > Is there a good place to look for documentation on > sysctl variables? man 3 sysctl didn't have anything about it. i noticed this by reading what could return ENOMEM in the mmap(2) page. other than that, i use the code and my co-workers. :-) _______________________________________________ Flow-tools mailing list [EMAIL PROTECTED] http://mailman.splintered.net/mailman/listinfo/flow-tools
