collectd-5.0.3 was released back in February. To compile (with my set of use flags) I needed a few patches changes: - [iptables] collectd-4.10.1-libiptc.patch does not apply anymore, to be replaced by upstream (but not released yet) commit 3835b23a2576a239f463b09edadf0dcde5d26f2d - [iptables] new collectd-5.0.3-iptc_handle.patch needed at least with net-firewall/iptables-1.4.12.1 which does not have typedefs for iptc_handle_t but just has struct iptc_handle - [netlink] collectd-4.10.3-netlink-attr-padding.patch starting with 3.3 kernel collectd's netlink plugin produces 3 lines of kernel log at each interval: netlink: 12 bytes leftover after parsing attributes. change netlink call to fix this. Note: this should eventually also be applied to 5.0.2 so early 3.3 kernel adopters don't get their (kernel)log spammed! Reproducible: Always
Created attachment 306225 [details, diff] Upstream commit 3835b23a2576a239f463b09edadf0dcde5d26f2d, replaces collectd-4.10.1-libiptc.patch
Created attachment 306227 [details, diff] Look for struct iptc_handle instead of (gone) iptc_handle_t
Created attachment 306231 [details, diff] Prevent (kernel)log spamming with >=3.3 kernel by netlink plugin
Ignore attachment #306227 [details, diff], it's not needed and was mis-guided on my part due to the configure failure du to commit 3835b23a2576a239f463b09edadf0dcde5d26f2d present in collect master branch but not in -5.0.3!
Thanks a lot for the patches. I'll have a look at it and report back.
We're skipping directly to 5.1.0 ... The libiptc patch should be obsolete then. Please submit the kernel-3.3 patch upstream; we'll add it as soon as it is accepted into git master.