Overview
Request 1008291 accepted
- Update to version 1.7.0.1
* Fix build issues in nfdump-1.7.0
- Drop patches:
* 0001-Add-missing-variable-initialization.patch
* 0002-Handle-fscanf-return-value-in-pidfile.c.patch
* 0003-Fix-snprintf-length-argument.patch
* fix-build.patch
- Update to version 1.7.0
* nfdump is now a multi-threaded program and uses parallel
threads mainly for reading, writing and processing flows as
well as for sorting. This may result in a 2 to 3 times faster
flow processing, depending on the tasks. The speed improvement
also heavily depends on the hardware (SSD/HD) and flow
compression option.
* For netflow v9 and IPFIX, nfdump now supports flexible length
fields. This improves compatibility with some exporters such
as yaf and others. The netflow v9 decoder is more flexible in
decoding.
* Support for Cisco Network Based Application Recognition (NBAR).
* Supports Maxmind geo location information to tag/geolocate IP
addresses and AS numbers.
* nfpcapd automatically uses TPACKET_V3 for Linux. This improves
packet processing. It adds new options to collect MAC and VLAN
information as well as the first packet of the payload.
* Metric exports: By default, every 60s a flow summary statistics
can be sent to a UNIX socket. The corresponding program may be
nfinflux to insert these metrics into an influxDB or nfexporter
for Prometheus monitoring.
- Add patches:
%config %{_sysconfdir}/nfdump.conf.dist
The filename usually indicates this isn't a user modified file, but rather a reference file. Really %config? Or is this only because RPM otherwise complains about a non-config file in /etc? ;-)
Hehe - of course I have only used it to get around the post build check warning:
[ 27s] nfdump.x86_64: W: non-conffile-in-etc /etc/nfdump.conf.dist
[ 27s] A non-executable file in your package is being installed in /etc, but is not a
[ 27s] configuration file. All non-executable files in /etc should be configuration
[ 27s] files. Mark the file as %config in the spec file.
I'm not sure how to handle this in a better way. We could also move this file could also move to %doc.
Any opinions on this ?
Well. Officially you should move it outside /etc. But I'd also make it similar to what you did. But I believe there is also a template mechanism. Have already seen it, but I handle so many packages that I don't remember where.
I'd add at least a comment in the spec file, so it can be fixed properly when someone knows how to do it :-)
Request History
mnhauke created request
- Update to version 1.7.0.1
* Fix build issues in nfdump-1.7.0
- Drop patches:
* 0001-Add-missing-variable-initialization.patch
* 0002-Handle-fscanf-return-value-in-pidfile.c.patch
* 0003-Fix-snprintf-length-argument.patch
* fix-build.patch
- Update to version 1.7.0
* nfdump is now a multi-threaded program and uses parallel
threads mainly for reading, writing and processing flows as
well as for sorting. This may result in a 2 to 3 times faster
flow processing, depending on the tasks. The speed improvement
also heavily depends on the hardware (SSD/HD) and flow
compression option.
* For netflow v9 and IPFIX, nfdump now supports flexible length
fields. This improves compatibility with some exporters such
as yaf and others. The netflow v9 decoder is more flexible in
decoding.
* Support for Cisco Network Based Application Recognition (NBAR).
* Supports Maxmind geo location information to tag/geolocate IP
addresses and AS numbers.
* nfpcapd automatically uses TPACKET_V3 for Linux. This improves
packet processing. It adds new options to collect MAC and VLAN
information as well as the first packet of the payload.
* Metric exports: By default, every 60s a flow summary statistics
can be sent to a UNIX socket. The corresponding program may be
nfinflux to insert these metrics into an influxDB or nfexporter
for Prometheus monitoring.
- Add patches:
dstoecker accepted request
@mnhauke: review reminder