From e454b4d34f31a644d1192904bde336f0f2d713fe Mon Sep 17 00:00:00 2001 From: Sebastian Hildebrandt Date: Sun, 17 Dec 2017 13:21:45 +0100 Subject: [PATCH] updated docs --- CHANGELOG.md | 1 + README.md | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index bd8f4e5..7a41244 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -99,6 +99,7 @@ Other changes | Version | Date | Comment | | -------------- | -------------- | -------- | +| 3.33.11 | 2017-12-17 | updated docs | | 3.33.10 | 2017-12-14 | bugfix WMIC blockDevice parse (Windows 7) | | 3.33.9 | 2017-12-14 | bugfix WMIC not found (Windows) | | 3.33.8 | 2017-12-02 | bugfix diskLayout().size (OSX) | diff --git a/README.md b/README.md index 7422b9b..cafa5f6 100644 --- a/README.md +++ b/README.md @@ -508,11 +508,11 @@ e.g. on DEBIAN based systems by running `sudo apt-get install lm-sensors` ## *: Additional Notes -In `fsStats`, `disksIO` and `networkStats` the results per second values (rx_sec, IOPS, ...) are calculated beginning +In `fsStats`, `disksIO` and `networkStats` the `results / sec.` values (rx_sec, IOPS, ...) are calculated correctly beginning with the second call of the function. It is determined by calculating the difference of transferred bytes / IOs divided by the time between two calls of the function. -The first time you are calling oe of this functions, you will get -1 for transfer rates. The second time, you should then get statistics based on the time between the two times … +The first time you are calling one of this functions, you will get -1 for transfer rates. The second time, you should then get statistics based on the time between the two calls … So basically, if you e.g. need a values for network stats every second, your code should look like this: