On 03/04/2017 11:02 AM, Galen Seitz wrote:
> On 03/04/17 00:41, Richard Owlett wrote:
>> On 03/02/2017 01:48 PM, Keith Lofstrom wrote:
>>> On Wed, Mar 01, 2017 at 04:33:57PM -0600, Richard Owlett wrote:
Is there a tool which can be
"turned on" at time t0
"turned off" at time t1
>>
On 03/04/2017 11:02 AM, Galen Seitz wrote:
> On 03/04/17 00:41, Richard Owlett wrote:
>> On 03/02/2017 01:48 PM, Keith Lofstrom wrote:
>>> On Wed, Mar 01, 2017 at 04:33:57PM -0600, Richard Owlett wrote:
Is there a tool which can be
"turned on" at time t0
"turned off" at time t1
>>
On 03/04/17 00:41, Richard Owlett wrote:
> On 03/02/2017 01:48 PM, Keith Lofstrom wrote:
>> On Wed, Mar 01, 2017 at 04:33:57PM -0600, Richard Owlett wrote:
>>> Is there a tool which can be
>>> "turned on" at time t0
>>> "turned off" at time t1
>>> which will report the number of
>>> "uploaded"
On 03/02/2017 01:48 PM, Keith Lofstrom wrote:
> On Wed, Mar 01, 2017 at 04:33:57PM -0600, Richard Owlett wrote:
>> 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 inter
On Wed, Mar 01, 2017 at 04:33:57PM -0600, Richard Owlett wrote:
> 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?
For your purposes, perhaps you pipe a standard in
On 03/01/2017 07:23 PM, King Beowulf wrote:
> On 03/01/2017 02:33 PM, Richard Owlett 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
>> trans
On 03/01/2017 07:18 PM, King Beowulf wrote:
> On 03/01/2017 02:33 PM, Richard Owlett 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
>> trans
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* verd
On 03/01/2017 02:33 PM, Richard Owlett 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
On 03/01/2017 02:33 PM, Richard Owlett 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
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.
>
> $ sudo cat /proc/net/dev
> Inter-| Receive| Transmit
> face |bytespackets err
Would /proc/net/dev give you the info you are looking for?
$ sudo cat /proc/net/dev
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed
multicast|bytespackets errs drop fifo colls carrier compressed
eth0: 168392
*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 Jess
13 matches
Mail list logo