summaryrefslogtreecommitdiff
path: root/net-analyzer/nethogs/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
committerV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
commit4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch)
treeba5f07bf3f9d22d82e54a462313f5d244036c768 /net-analyzer/nethogs/metadata.xml
reinit the tree, so we can have metadata
Diffstat (limited to 'net-analyzer/nethogs/metadata.xml')
-rw-r--r--net-analyzer/nethogs/metadata.xml20
1 files changed, 20 insertions, 0 deletions
diff --git a/net-analyzer/nethogs/metadata.xml b/net-analyzer/nethogs/metadata.xml
new file mode 100644
index 000000000000..1b55544df345
--- /dev/null
+++ b/net-analyzer/nethogs/metadata.xml
@@ -0,0 +1,20 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="project">
+ <email>netmon@gentoo.org</email>
+ <name>Gentoo network monitoring and analysis project</name>
+ </maintainer>
+ <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 indentify
+programs that have gone wild and are suddenly taking up your bandwidth.
+ </longdescription>
+ <upstream>
+ <remote-id type="sourceforge">nethogs</remote-id>
+ <remote-id type="github">raboof/nethogs</remote-id>
+ </upstream>
+</pkgmetadata>