Red Hat Bugzilla – Bug 491240
Review Request: dropwatch - monitor for dropped network packets in the kernel
Last modified: 2009-04-08 07:43:47 EDT
Dropwatch is the user space utility that interfaces to a new kernel netlink protocol for the purposes of monitoring the linux network stack for dropped packets.
also, I found spec is not following packaging guidelines
1) use valid buidlroot value from
2) use macros as given at https://fedoraproject.org/wiki/Packaging/RPMMacros
3) compiler flags are not used.
4) License should be GPLv2+
5) rpmlint gave
dropwatch.i386: W: non-standard-group Applications/Utilities
Got one more query not related to packaging but I think ifconfig also gives count of dropped packets. Summary of this package is " Kernel dropped packet monitor" then what is difference between dropped packets counted by ifconfig and this dropwatch utility?
Thank you. New package for review
Regarding the difference between dropwatch and ifconfig, its all written up on the hosted page:
Ifconfig measures dropped packets in the hardware and driver of a specific interface, while dropwatch monitors them throughout the network stack, disambiguating their location and cause.
unable to download Source tarball.
sorry, built it on an F-10, rather than F-9 System. My bad. New links below:
But how can I download source used to build this package?
gave ERROR 404: Not Found.
sorry I mean to say
Thats odd, I'm sorry. My makefiles must have been messed up. The source tarball is there now:
Note its dropwatch-1.0.tbz2, not .tar.gz
reverifying source tarball with packaged tarball in SRPM
md5sum failed to verify tarball.
Can you please remove srpm and again tarball with same name from tarball dropwatch-1.0.tbz2?
sorry, stupid build environment glitch. New links to fix that:
+ package builds in mock (rawhide i586).
koji build => http://koji.fedoraproject.org/koji/taskinfo?taskID=1255875
+ rpmlint output for SRPM and for RPM.
dropwatch.i586: E: explicit-lib-dependency libnl
==> Can be ignored
+ source files match upstream url
+ package meets naming and packaging guidelines.
+ specfile is properly named, is cleanly written
+ Spec file is written in American English.
+ Spec file is legible.
+ dist tag is present.
+ build root is correct.
+ license is open source-compatible.
+ License text is included in package.
+ BuildRequires are proper.
+ defattr usage is correct.
+ %clean is present.
+ package installed properly.
+ Macro use appears rather consistent.
+ Package contains code, not content.
+ no headers or static libraries.
+ no .pc file present.
+ no -devel subpackage
+ no .la files.
+ no translations are available.
+ Does owns the directories it creates.
+ no scriptlets present.
+ no duplicates in %files.
+ file permissions are appropriate.
+ Not a GUI App.
Can you also tell me how to test dropwatch and can it be possible to test on F10?
on F10 when I ran dropwatch I got
Unable to find NET_DM family, dropwatch can't work
Cleaning up on socket creation error
Yeah, you'll be able to test on F-10 and rawhide shortly. Dropwatch needs some kernel bits that I wrote to work properly. Specifically, it needs these patches, which are slated for 2.6.30:
I'm working on getting them backported for rawhide and F-10. I'll provide you a pointer to my koji builds as soon as I have them.
Thanks for above information.
New Package CVS Request
Package Name: dropwatch
Short Description: dropwatch is a monitor used to detect dropped packets in the linux networking stack
Branches: devel F-10
If this is built for all requested branches then can we have this closed now?