Cameron Sparr 5af5f08785 Fix NetIOCounter windows interface behavior ...

addresses a few things:

- Windows has a concept of both a network "interface" and an "adapter"
- These are almost always a one-to-one relationship, though there can be
esoteric instances where they are not.
- I believe the gopsutil NetIOCounters function should only return on a
per-interface level, since this is the behavior on linux/darwin.

Previously, the plugin was basically ignoring the actual interfaces
returned from net.Interfaces(). Instead, it was looping over the net
adapters for each interface, somewhat uselessly.

FWIW, the code for getAdapterList() doesn't exist in the Go standard lib
anymore.

closes #245

2016-10-25 16:51:40 +01:00

..

net_darwin_test.go

only run ifconfig/netstat if necessary, add some tests

2016-09-04 16:37:28 +02:00

net_darwin.go

only run ifconfig/netstat if necessary, add some tests

2016-09-04 16:37:28 +02:00

net_fallback.go

Add fallback code for all unsupported operating systems.

2016-08-22 15:31:26 -07:00

net_freebsd.go

add Timeout to invoke command and use common.Invoke refs: #201

2016-05-20 17:59:41 +09:00

net_linux_test.go

[net]linux: add a test and fix private field name.

2016-03-10 22:32:16 +09:00

net_linux.go

remove unused code

2016-10-11 10:34:47 +02:00

net_test.go

fix net_test.go

2016-10-06 15:46:14 +02:00

net_unix.go

fixed by golint.

2016-04-01 21:34:39 +09:00

net_windows.go

Fix NetIOCounter windows interface behavior

2016-10-25 16:51:40 +01:00

net.go

add Uids field to net_linux

2016-10-06 14:50:03 +02:00