-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi.
Anyone here had any issues with the length of filters used by nfdump 1.5.7? I know the manpage states that there isn't any limits, but I believe there is. I have a filter consisting of 17655 characters (as calculated by wc -m) on the form (ip x.x.x.x and port xxxxx) or (ip x.x.x.x and port xxxxx) or ...etc. When I run nfdump as shown here; nfdump -R router01/2008/12/02/nfcapd.200812021200:nfcapd.200812021800 -f <path_to_filter_file> it is as if nfdump totally ignores it. If I remove some characters, getting the total number below or equal to 17627, everything works perfectly. This issue would seem to be specific to the -f option only, because if I take my 17655-chars filter and append it directly as an argument, the filter is correctly applied. Could someone else please confirm this, or perhaps I've got some gremlins in my server :) Regards, Tor I. Skaar -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk1vV0ACgkQ6kzbtNj+3wMCWwCdFatbDH9+4MWpP6a0JhJ5xQKw L6wAoLsUBcI7BBuoRRr5hG6YBbUlKul7 =QSKP -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
