Fix parsing of free -m for motd generation
#228
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix the awk scripts used in /etc/update-motd.d/50-scw for parsing the output of `free -m`. They used to always report "0.0%" memory and swap usage.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When logging into a Debian 10 instance, one is greeted with some system information including:
The meters always display
0.0%, irrespective of the actual usage. These numbers are generated in /etc/update-motd.d/50-scw by awk scripts that incorrectly parse parse the output offree -m.This pull request fixes those scripts. It has been tested on a Debian 10 Scaleway instance and on an Ubuntu 18.04 desktop (tested the parsing of
free -m).