Arnout Engelen 4182fc0b17 * when a packet's owner cannot be found (for example if it has already disappeared,
which can happen with for example small fast HTTP requests), show the source and
  destination ports and ip's
* support UDP packets (which never have owners)
* nicely truncate oversized program names
2005-08-27 11:49:16 +00:00
2004-09-18 12:25:53 +00:00
2004-09-17 19:23:20 +00:00
2005-04-03 09:49:34 +00:00
2004-09-15 12:49:05 +00:00
2004-09-14 19:24:01 +00:00
2004-06-29 13:31:04 +00:00
2004-06-29 13:31:04 +00:00
2005-07-24 16:14:51 +00:00
2004-06-29 13:31:04 +00:00
2004-09-14 19:24:01 +00:00
2004-08-23 09:48:43 +00:00
2005-07-24 16:14:51 +00:00
2004-06-29 13:31:04 +00:00
2004-06-29 13:31:04 +00:00
2004-06-29 13:31:04 +00:00
2004-06-29 13:31:04 +00:00

= NETHOGS =

http://nethogs.sf.net

== INTRODUCTION ==

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.

Since NetHogs heavily relies on /proc, it currently runs on Linux only. 

== STATUS ==

Ideas/ToDo for new releases:

* Only IPv4 TCP is currently supported
* Sort the output by other values than network usage
* Monitor specific processes
* Make it work correctly on machines with multiple IP addresses
* Integrate into another tool?? 

== LICENSE ==

GPL.
Description
No description provided
Readme 1.2 MiB
Languages
C++ 58.5%
HTML 18.1%
C 10.4%
Python 4.3%
Shell 3.8%
Other 4.9%