Yes, just remove these. There are more in src/service.c to chop.
Okay, I'll spin a few patches for it.
> connmand: src/dnsproxy.c:forward_dns_reply() Received 146
> bytes (id 0x015a)
> connmand: src/dnsproxy.c:udp_listener_event() Received 37
> bytes (id 0x7bb2)
> I did a quick hack to get a discussion going on the idea to support
> debug levels? What do you think on this?
At least the aboe low-level dnsproxy ones make sense with -d
My point is that if you provide only '-d' we get those low level
dnsproxy DBGs which spam the output.
Another idea would be to enable low level debugs only on exact match,
e.g only show them if '-d src/dnsproxy.c' was given and not on '-d'.
> Or should I just do the same with dnsproxy as we have with these
> README: CONNMAN_DHCP_DEBUG DHCPv4 related debug information
> README: CONNMAN_DHCPV6_DEBUG DHCPv6 related debug information
> README: CONNMAN_IPTABLES_DEBUG Extra information when iptables is used
> README: CONNMAN_RESOLV_DEBUG Name resolver debug prints. These debug prints
> README: CONNMAN_SUPPLICANT_DEBUG Debugging prints for communication between
> README: CONNMAN_WEB_DEBUG Debug information when ConnMan does Internet
The CONNMAN_*_DEBUG were used for the "external" components in ./gdhcp,
./gsupplicant and ./gweb. The rest in ./src and ./plugins follow the -d
Ah yes, that was the reason for those ones. Well, if we would have the
concept of exact match we could apply it to these ones as well.
(and it seems I forgot to add CONNMAN_NFTABLES_DEBUG)