https://bugzilla.netfilter.org/show_bug.cgi?id=1060
Bug ID: 1060
Summary: Garbage output
Product: libnetfilter_log
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: libnetfilter_log
Assignee: netfilter-buglog at lists.netfilter.org
Reporter: roa at eurotux.com
libnetfilter_log produces lots of garbage to stdout, making programs that use
its functions do that too.
How to reproduce:
# iptables -I INPUT -j NFLOG --nflog-group 16
# iptables -I FORWARD -j NFLOG --nflog-group 16
# iptables -I OUTPUT -j NFLOG --nflog-group 16
# /usr/bin/fprobe-ulog 127.0.0.1:8818/127.0.0.1 -n7 -U32768 -l2
[INFO]: Starting 1.2...
[INFO]: pid: 26971
[INFO]: options: u=32768 s=5 g=30 d=60 e=300 n=7 a=0.0.0.0 M=0 b=10000 m=0
q=100 B=0 r=0 t=0:0 c= u= v=6 l=2
[INFO]: collector #1: 127.0.0.1:8818/127.0.0.1/m
first
next
next
next
next
next
next
next
next
next
first
next
next
next
first
next
next
next
first
next
next
next
^C
After a while, it's a complete log clutter and waste of resources.
The problem is present in the latest git version, but seems to have been there
for a while:
$ grep -n 'printf.*\(first\|next\)' src/*
src/libipulog_compat.c:136: printf("first\n");
src/libipulog_compat.c:139:next_msg: printf("next\n");
Those printfs seem to have been forgotten when debugging, I'd say.
Sure it's possible to workaround (redirecting the output somewhere in the
middle?) but the methods aren't exactly desirable so I'd recommend
fixing this.
Best regards.
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20160331/5c62eb8a/attachment.html>
