[mrtg] bytes v/s bits

[Steve Shipway]

> Problem is placement of the --global clause. Early in the cfgmaker command
> works but after the community at ip fails!
>
> Worth fixing....

This is actually by design, and mentioned in the cfgmaker documentation (although possibly not very clearly).

The various cfgmaker options, like --global, only apply to community at host entries AFTER them in the list.  So, the safest way is to make sure all your options come first, and the community at host list comes last.

The reason for this is so that you can give different options and parameters to multiple hosts in the cfgmaker list.  However since it is considered best practice to have one cfg file per host you will probably only have one community at host entry in the list anyway.

Steve