diff --git a/glances/outputs/static/js/components/plugin-cpu/controller.js b/glances/outputs/static/js/components/plugin-cpu/controller.js index 44090d2a..7a6e0bbf 100644 --- a/glances/outputs/static/js/components/plugin-cpu/controller.js +++ b/glances/outputs/static/js/components/plugin-cpu/controller.js @@ -28,6 +28,8 @@ export default function GlancesPluginCpuController($scope, GlancesStats) { var stats = data.stats['cpu']; _view = data.views['cpu']; + vm.isLinux = data.isLinux; + vm.total = stats.total; vm.user = stats.user; vm.system = stats.system; diff --git a/glances/outputs/static/js/components/plugin-cpu/view.html b/glances/outputs/static/js/components/plugin-cpu/view.html index ac6fd4d8..265adc7e 100644 --- a/glances/outputs/static/js/components/plugin-cpu/view.html +++ b/glances/outputs/static/js/components/plugin-cpu/view.html @@ -72,7 +72,7 @@ {{ vm.soft_interrupts }} -
\n * In plain HTML forms, the `name` attribute is used to identify groups of radio inputs, so\n * that the browser can manage their state (checked/unchecked) based on the state of other\n * inputs in the same group.\n *
\n *\n * In AngularJS forms, this is not necessary. The input's state will be updated based on the\n * value of the underlying model data.\n *
\n *