Argus memory issues
Carter Bullard
carter at qosient.com
Fri Aug 24 12:15:49 EDT 2007
Excellent, well thats good news. I have a little work to do this weekend,
and then we should have a very efficient argus-3.0.0. Probably worth the
wait, before release, but we need to be zipping this thing up really
soon. I'll
try to back out of argus-clients-3.0.0.rc.48 to rc.47, and hopefully
that will
get us to a working set.
Any sense of cpu load and memory use comparisons with argus-2.x?
What we don't have in the current small memory implementation:
1. argus output filtering (that comes next)
2. jitter implementaion (it seems particularly memory hungry)
3. efficient multiple client access
I will need to migrate the new memory model to radium() as it needs to do
this as well, and so there is a little work to do still.
Glad to hear that things are better,
Carter
Peter Van Epp wrote:
> And the data in the files is looking good too. I don't see any missing
> time stamps (a perl script to check all of them is in order though :-)) and
> I'm not seeing the time stamps from the last hour that I was before, all the
> time stamps that I saw seem to be around the current time as I would expect.
> However the -U flag doesn't seem to be working:
>
> argus -JR -P 560 -i eth0 -i eth1 -U 512 -m -F /scratch/argus.conf
>
> test4:/var/log/argus vanepp$ /usr/local/src/argus-clients-3.0.0.rc.48/bin/ra -r com_argus -s +suser:512 +duser:512 -n
> 07-08-24 07:59:58 e tcp 60.50.152.40.1650 <?> 142.58.101.50.25 3 5 180 449
> 07-08-24 07:59:55 e tcp 84.181.182.190.63877 <?> 142.58.101.50.25 4 4 275 408
> 07-08-24 07:59:55 e tcp 142.58.107.55.1675 <?> 205.147.84.41.80 2 1 120 60
> 07-08-24 07:59:55 e tcp 220.189.218.122.8427 <?> 142.58.101.27.8080 6 6 621 2037
>
>
> Peter Van Epp / Operations and Technical Support
> Simon Fraser University, Burnaby, B.C. Canada
>
>
More information about the argus
mailing list