Your limits need to be set in /etc/login.conf. One quick way to do
this is put yourself into the "root" login class.
You may also need to use a custom kernel with MAXDSIZ set high.
options MAXDSIZ="(2000*1024*1024)"
# limits
Resource limits (current):
cputime infinity secs
filesize infinity kb
datasize 2048000 kb
stacksize 65536 kb
coredumpsize infinity kb
memoryuse-cur 786432 kb
memorylocked infinity kb
maxprocesses-cur 128
openfiles-cur 1024
sbsize infinity bytes
vmemoryuse infinity kb
--
mark
On Sep 28, 2004, at 9:38 PM, Gavin Cato wrote:
Hiya,
I wrote a simple perl program that reads in a list of customer config
files,
and then generates an appropriate config file for flow-report to read
with
the "-s" flag.
It works fine, but when the config file starts to have a reasonable
amount
of report commands in it, I get a error when it tries to run after a
few
seconds.
running flow-cat
/storage/netflow/2004/2004-09/2004-09-29/ft-v05.2004-09-29.000000+1000
|
flow-report -s /tmp/report.conf.65545 -S flow-report
flow-report: malloc()
flow-report: ftchash_alloc_rec(): failed
flow-report: ftch_update(): failed
flow-report: f_accum(iht-inbound): failed.
flow-report: ftstat_eval(flow-report): failed.
The report.conf file specified in the command does appear ok - just
largish.
I can post it if someone likes.
This is running under FreeBSD 4.10 with 2gb ram on a 2.8 P4.
Any help would be greatly appreciated.
Gav
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
