ra as a long running task

[Carter Bullard via Argus-info]

Hey Brad,
Try the latest in the development section.  May be s fix already in the codebase.

   http://qosient.com/argus/dev/argus-clients-latest.tar.gz

Carter

> On May 4, 2016, at 2:01 PM, Brad <brad at vt.edu> wrote:
> 
>> On 05/04/2016 10:05 AM, Carter Bullard wrote:
>> Hey Brad,
>> Shouldn’t be any memory leaks.  What version are you running ???
>> 
>> If you want to permanently collect from argus, definitely use radium as
>> that provides multi-access to the argus stream.  It also allows you to
>> collect from multiple sources, so I would suggest that you think about
>> radium.
>> 
>> Carter
>> 
>>> On May 4, 2016, at 9:06 AM, Brad via Argus-info
>>> <argus-info at lists.andrew.cmu.edu
>>> <mailto:argus-info at lists.andrew.cmu.edu>> wrote:
>>> 
>>> Is ra meant to be used for long running tasks?
>>> 
>>> When I run it to read  from a socket (see below) for an extended
>>> period (a few days) memory usage slowly grows to 100% and the process
>>> dies.
>>> 
>>> ra -c, -L-1 -nn -p 3 -Zs -s stime ltime dur saddr daddr sport dport
>>> state proto spkts sbytes dbytes -S argus_sensor:5050
>>> 
>>> If ra should work acceptably in this situation, I can debug more and
>>> find the cause of the memory leak. If it is not meant for this
>>> purpose, what should I use instead of ra. radium?
>>> 
>>> Thanks,
>>> 
>>> Brad
> 
> Hey Carter,
> 
> /usr/local/bin/ra --version
> Ra Version 3.0.8
> 
> Brad
>