[Oisf-devel] Mem leaks

Martin Holste mcholste at gmail.com
Thu Oct 6 15:47:50 UTC 2011


Nope, that doesn't fix it:
[1360] 6/10/2011 -- 10:44:46 - (flow-timeout.c:567) <Error>
(FlowForceReassemblySetup) -- [ERRCODE: SC_ERR_TM_MODULES_ERROR(135)]
- Looks like we have failed to retrieve the slot for DECODE TM

If you have a space between the hyphen and interface as you wrote, it
doesn't even parse the config.

On Thu, Oct 6, 2011 at 10:40 AM, Martin Holste <mcholste at gmail.com> wrote:
> Ah, gotta love it when the fix is easy!  I suppose ideally the config
> would accept either or throw a better warning.
>
> On Thu, Oct 6, 2011 at 10:37 AM, Eric Leblond <eric at regit.org> wrote:
>> Hello,
>>
>> On Thu, 2011-10-06 at 10:31 -0500, Martin Holste wrote:
>>> pfring:
>>>   threads: 8 #1
>>>  interface: eth4
>>>   cluster-id: 99
>>>   cluster-type: cluster_flow
>>
>> Thanks, I able to reproduce the issue and I will work on it now. This
>> seems to be related with backward compatibility of configuration file.
>>
>> For your setup, the new configuration format is:
>>
>> pfring:
>> - interface: eth4
>>  threads: 8
>>  cluster-id: 99
>>  cluster-type: cluster_flow
>>
>> The advantage of this new format you can specify multiple interfaces
>> with different parameters.
>>
>> BR,
>> --
>> Eric Leblond
>> Blog: http://home.regit.org/
>>
>



More information about the Oisf-devel mailing list