Graph template 'Linux - Memory Usage' has the wrong unit on its vertical_label

[YongBoLiu]

Describe the bug
A clear and concise description of what the bug is.
The vertical_label unit kilobytes is wrong on graph template 'Linux - Memory Usage' . It should be Bytes.
When my Linux cacti server has 23G memory free. The graph shows 23G, which is OK. But the vertical lable show kilobytes. It's wrong, should be Bytes.

To Reproduce
Steps to reproduce the behavior:

1. Go to Console->graphs.
2. Click on the Local Linux Machine - Memory Usage graph.
3. Check the vertical lable on the graph.

Expected behavior
A clear and concise description of what you expected to happen.
Change the kilobytes to Bytes.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]
  Linux

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

The script (#perl cacti/scripts/linux_memory.pl) returns value in KB, and the graph item use 'Multiply by 1024'. So, the value result in Bytes.

The file Local_Linux_Machine.xml seems be encoded, after gzip the cacti/install/templates/Local_Linux_Machine.xml.gz.

[YongBoLiu]

[netniV]

So, one of two things is wrong then, either the label should become bytes or the values should have been divided by 1024 but are not... Not sure if @cigamit changed that in the last year or not without searching which I can't do right now.

[YongBoLiu]

@netniV I prefer to change the label to bytes, because this makes the value more straightforward. Otherwise, we may get the value, 3G as shown 3M of KB. Thanks.

[netniV]

Yeah I can agree with that assume the label doesn't adjust itself which your example suggests it does not.

[cigamit]

This is resolved now with the updated Local Linux Machine package.

[netniV]

One thing is that we may need to make the installer allow re-installation of packages

[cigamit]

We really need a 'Package' option on the Import/Export page as well, one that can install packages from a local file system, or directly download and install them from GitHub. But instead of making a new option, we just allow them to specify package or template on the import export picks.