Rare project developers

[Frédéric LOUI <>]

> Those have their own independet timers since they are running as
> separate threads. There is no need to express them relative to the
> interface status interval, I think.
Fair enough !

Thanks again
Frederic

> Le 18 mars 2022 à 10:52, Alexander Gall <> a écrit :
> 
> On Fri, 18 Mar 2022 10:27:20 +0100, Frédéric LOUI 
> <> said:
> 
>> Hi,
>> Previous behaviour:
>> Interface status check -> 1s
>> Other counters -> 1s (x5) 
>> Other counters are 1s (x30)
> 
>>> https://bitbucket.software.geant.org/projects/RARE/repos/rare/commits/b5df56af79fe20909105fdcb4b674843886faa1c
> 
>> Super ! These can be the default one and I suggest 3 additional parameters:
> 
>> - One for interface status
>> - One for interface/subinterface counter
>> - One for the counter (nat/nsh/flowspec/acl_[in}out] etc. )
> 
> 
>> Or:
>> - One for reference period: 1s
>> - One for interface/subinterface counter multiple: ref_period x5 (for 
>> example)
> 
> Yes, That's what we have now :)
> 
>> - One multiple for other counters: ref_period x30 (for example)
> 
> Those have their own independet timers since they are running as
> separate threads. There is no need to express them relative to the
> interface status interval, I think.
> 
> -- 
> Alex