>
> |>>
> |>> Thanks
> |>>
> |> Hi Jose,
> |>
> |> It think the cause of your problem lies in the naming of your channel.
> |> If I do:
> |>
> |> nfdump -Z "ident 182"
> |>
> |> the result is:
> |>
> |> line 1: syntax error at '182'
> |>
> |> And because nfprofile uses the same parser, it bails out silently
> |> during the profiler phase.
> |>
> |> I walked into a similar problem some time ago with channels called
> |> 'in' and 'out'. According to grammar.y, 'ident' should be followed by
> |> a string, but '182' is recognized as an integer. Values like 'in',
> |> 'out' and 'tcp' are considered filter primitives. And both integers
> |> and filter primitives are not considered strings. My quick and dirty
> |> solution was simply renaming the channels, but maybe this issue
> |> requires some more attention? Note that NfDump 1.5.6 and before did
> |> accept filter primitives as valid values for the ident field (I don't
> |> know if it handles integers).
> |
> | Werner,
> |
> | That made the trick. That was a weird error/bug/feature.
> | I reconfigure my nfsen.conf to complete names, including letters,
> | deleted old profiles and created new ones, and everything is working as
> | it is supposed to.
> |
>
> Well - I need to check, how to prevent these errors. That's indeed a 
> bit ugly.
> Thanks for all the input and sorry for the trouble.
>
>     - Peter

Your software is excellent, no questions about it.
Thanks to you for your feedback.

- Jose

>
> | Thanks a lot for everybody's comments and help.
> |
> | Great community around a marvelous software.
> |
> | Regards,
> |
> | - Jose
> |
> |> - Werner
> |>>
> |>>> Jose
> |>>>


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss

Reply via email to