Only parse a single line from lscpu to get the Cpu(s) count. #879
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.
Dear Discourse maintainers,
This is intended to fix an error I was getting with
discourse-setup
on Debian, from line 261:Caused by the parsing of
lscpu
command retaining 2 lines instead of just the intended one.This occurs on my PCs with Debian testing (lscpu from util-linux 2.40.2) and Debian stable (util-linux 2.38.1) because it outputs a line formatted like this (in the "Vendor" section):
(I also checked on a machine with CentOS, there the format is
CPU MHz: 2700.000
).To avoid that, I made the regex more specific, but I also added an
exit
statement inawk
. Probably just one of these fixes could be used.I believe the script would have worked with the version prior to this commit from a month ago: d00c2e7
Best,