On 03/01/2017 05:32 PM, Richard Owlett wrote:
> On 03/01/2017 04:44 PM, Robert Citek wrote:
>> Would /proc/net/dev give you the info you are looking for?
>
> I don't know.
> Will investigate when awake.
> Thank you.

A good night's sleep and a cup of coffee (even if decaf) yields a 
*POSITIVE* verdict. It and some simple scripts will allow me record with 
appropriate resolution/granularity different processes which could last 
from minutes to hours. It seems "made for" the problem that prompted my 
question.


>
>
>>
>> $ sudo cat /proc/net/dev
>> Inter-|   Receive                                                |  Transmit
>>  face |bytes    packets errs drop fifo frame compressed
>> multicast|bytes    packets errs drop fifo colls carrier compressed
>>   eth0: 16839226   26454    0    0    0     0          0         0
>> 16903410   27268    0    0    0     0       0          0
>>   eth1:       0       0    0    0    0     0          0         0
>> 578       7    0    0    0     0       0          0
>>     lo:       0       0    0    0    0     0          0         0
>>   0       0    0    0    0     0       0          0
>>
>> Capture at t0 and t1, parse, diff.
>>
>> Regards,
>> - Robert
>>
>> On Wed, Mar 1, 2017 at 2:33 PM, Richard Owlett <rowl...@cloud85.net> wrote:
>>> *NOTE BENE*
>>> Capitalization in subject line semantically important :>
>>>
>>> I have significant bandwidth constraints.
>>> I have been asked to participate in a project requiring significant data
>>> transfers.
>>> I wish to run a test case to estimate the connectivity "cost".
>>> If it is significant, I use Debian Jessie.
>>> For the test case the source/destination is of secondary importance.
>>>
>>> Is there a tool which can be
>>>   "turned on"  at time t0
>>>   "turned off" at time t1
>>> which will report the number of
>>>    "uploaded"   bytes
>>>    "downloaded" bytes
>>> in that interval?
>>>
>>> If the tool reports more, no problem -- it will likely be ignored.
>>> TIA
>>>
>>> _______________________________________________
>>> PLUG mailing list
>>> PLUG@lists.pdxlinux.org
>>> http://lists.pdxlinux.org/mailman/listinfo/plug
>> _______________________________________________
>> PLUG mailing list
>> PLUG@lists.pdxlinux.org
>> http://lists.pdxlinux.org/mailman/listinfo/plug
>>
>
>
> _______________________________________________
> PLUG mailing list
> PLUG@lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>


_______________________________________________
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to