2016-01-14 19:47:55 +00:00
|
|
|
{ stdenv, fetchFromGitHub, ncurses, libpcap }:
|
2014-04-23 16:51:14 +01:00
|
|
|
|
|
|
|
stdenv.mkDerivation rec {
|
|
|
|
name = "nethogs-${version}";
|
2016-01-14 19:47:55 +00:00
|
|
|
version = "0.8.1";
|
2014-04-23 16:51:14 +01:00
|
|
|
|
2016-01-14 19:47:55 +00:00
|
|
|
src = fetchFromGitHub {
|
|
|
|
owner = "raboof";
|
|
|
|
repo = "nethogs";
|
|
|
|
rev = "v${version}";
|
|
|
|
sha256 = "1phn6i44ysvpl1f54bx4dspy51si8rc2wq6fywi163mi25j355d4";
|
2014-04-23 16:51:14 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
buildInputs = [ ncurses libpcap ];
|
|
|
|
|
2016-01-14 19:47:55 +00:00
|
|
|
installFlags = [ "prefix=$(out)" "sbin=$(prefix)/bin" ];
|
2014-04-23 16:51:14 +01:00
|
|
|
|
|
|
|
meta = with stdenv.lib; {
|
|
|
|
description = "A small 'net top' tool, grouping bandwidth by process";
|
|
|
|
longDescription = ''
|
|
|
|
NetHogs is a small 'net top' tool. Instead of breaking the traffic down
|
|
|
|
per protocol or per subnet, like most tools do, it groups bandwidth by
|
|
|
|
process. NetHogs does not rely on a special kernel module to be loaded.
|
|
|
|
If there's suddenly a lot of network traffic, you can fire up NetHogs
|
|
|
|
and immediately see which PID is causing this. This makes it easy to
|
|
|
|
identify programs that have gone wild and are suddenly taking up your
|
|
|
|
bandwidth.
|
|
|
|
'';
|
|
|
|
license = licenses.gpl2Plus;
|
|
|
|
homepage = http://nethogs.sourceforge.net/;
|
|
|
|
platforms = platforms.linux;
|
2016-01-14 19:47:55 +00:00
|
|
|
maintainer = [ maintainers.rycee ];
|
2014-04-23 16:51:14 +01:00
|
|
|
};
|
|
|
|
}
|