Comment 2 for bug 578377

A configurable parameters will be fine. But I want to argue the
Bps/bps as following:

wget/curl/rsync shows bytes make sense because they mainly deal with
"Files" which usually save on disk that being present in bytes.

How ever, monitoring network traffic is usually represent by bps. For
example an adsl line have 2Mbps limitation, your shared vps have
200Gbps traffic quota, and when you shaping your traffic using TC, it
still in bps. All network monitoring tools report in bps.

So here you can see, Bps/bps usually serve different purpose and
believe it will be more nature to see them in bps.

On Mon, May 10, 2010 at 2:58 PM, Dustin Kirkland
<email address hidden> wrote:
> Hmm, really?
>
> wget, curl, rsync all show bytes-per-second  by default.
>
> I'm quite happy with bytes-per-second.
>
> Would you like a configuration parameter to switch everything to bits?
> If so, what all would you want to see in bits?
>
> ** Changed in: byobu
>       Status: New => Invalid
>
> --
> Use bps instead of Bps in network monitoring
> https://bugs.launchpad.net/bugs/578377
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in byobu: Invalid
>
> Bug description:
> The network monitoring should use bps (bit per second) by default, althrough it needs the value to be mutiply by 8.
>
> It's a lot of userful to see it in bps since almost all network restrictions come in bps not byte-per-second value.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/byobu/+bug/578377/+subscribe
>