Chris sorry for the delay, please update from svn, you can use "dnacl*" instead of "dnacluster" now.
Regards Alfredo On Oct 10, 2012, at 9:16 PM, Chris Wakelin <[email protected]> wrote: > I've been hitting problems with 12 cores and Suricata's thread names > again. Did you come to a conclusion about having "dnacl" instead of > "dnacluster" in interface names? > > For now I've hacked the Suricata source to rename receive thread names > from RxPFR<ifname> to just RPF<ifname> and they now fit. > > Best Wishes, > Chris > >> Re: PF_RING libzero and legacy apps [In reply to] > >> On May 30, 2012, at 12:53 PM, Chris Wakelin wrote: > >>>> Another minor issue is that Suricata's statistics truncate the interface >>>> name and so missed the "@0"..."@5" at the end, so I couldn't easily >>>> split out what each queue saw. >>> >>> Suricata truncates interface names > 15 chars in it's thread-naming, so >>> choosing a single-digit cluster ID made it fit. It might cause less such >>> compatibility issues though to have a shorter name for the cluster >>> interface, say dnacl:X@Y ? >> >> Ok, we will definitely consider this. >> >> Best Regards >> Alfredo > > -- > --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- > Christopher Wakelin, [email protected] > IT Services Centre, The University of Reading, Tel: +44 (0)118 378 2908 > Whiteknights, Reading, RG6 6AF, UK Fax: +44 (0)118 975 3094 > _______________________________________________ > Ntop-misc mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop-misc _______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
