Gentoo Archives: gentoo-commits

From: David Seifert <soap@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nethogs/
Date: Sun, 26 Nov 2017 23:11:33
Message-Id: 1511737806.6fecdec4263a91a3c954087671aa2063604b81c1.soap@gentoo
1 commit: 6fecdec4263a91a3c954087671aa2063604b81c1
2 Author: David Seifert <soap <AT> gentoo <DOT> org>
3 AuthorDate: Sun Nov 26 12:38:37 2017 +0000
4 Commit: David Seifert <soap <AT> gentoo <DOT> org>
5 CommitDate: Sun Nov 26 23:10:06 2017 +0000
6 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6fecdec4
7
8 net-analyzer/nethogs: [QA] Consistent whitespace in metadata.xml
9
10 net-analyzer/nethogs/metadata.xml | 14 +++++++-------
11 1 file changed, 7 insertions(+), 7 deletions(-)
12
13 diff --git a/net-analyzer/nethogs/metadata.xml b/net-analyzer/nethogs/metadata.xml
14 index 1b55544df34..03dae9d25e4 100644
15 --- a/net-analyzer/nethogs/metadata.xml
16 +++ b/net-analyzer/nethogs/metadata.xml
17 @@ -1,4 +1,4 @@
18 -<?xml version='1.0' encoding='UTF-8'?>
19 +<?xml version="1.0" encoding="UTF-8"?>
20 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
21 <pkgmetadata>
22 <maintainer type="project">
23 @@ -6,12 +6,12 @@
24 <name>Gentoo network monitoring and analysis project</name>
25 </maintainer>
26 <longdescription>
27 -NetHogs is a small 'net top' tool. Instead of breaking the traffic down
28 - per protocol or per subnet, like most tools do, it groups bandwidth by
29 -process. NetHogs does not rely on a special kernel module to be loaded.
30 -If there's suddenly a lot of network traffic, you can fire up NetHogs and
31 -immediately see which PID is causing this. This makes it easy to indentify
32 -programs that have gone wild and are suddenly taking up your bandwidth.
33 + NetHogs is a small 'net top' tool. Instead of breaking the traffic down
34 + per protocol or per subnet, like most tools do, it groups bandwidth by
35 + process. NetHogs does not rely on a special kernel module to be loaded.
36 + If there's suddenly a lot of network traffic, you can fire up NetHogs and
37 + immediately see which PID is causing this. This makes it easy to indentify
38 + programs that have gone wild and are suddenly taking up your bandwidth.
39 </longdescription>
40 <upstream>
41 <remote-id type="sourceforge">nethogs</remote-id>