Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: 9032394aca73cc9610b76f21bd74886fc33035b3
https://github.com/tribe29/checkmk/commit/9032394aca73cc9610b76f21bd74886fc…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2020-09-10 (Thu, 10 Sep 2020)
Changed paths:
M agents/check_mk_agent.openwrt
Log Message:
-----------
Shell format fix agent openwrt
Change-Id: I25f72632a1127b626f28e176929e620d12f6fac2
Commit: 65c483629ae2c0dbe9038633dc3584c3e550acf9
https://github.com/tribe29/checkmk/commit/65c483629ae2c0dbe9038633dc3584c3e…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2020-09-10 (Thu, 10 Sep 2020)
Changed paths:
A .werks/11392
M agents/check_mk_agent.linux
M agents/check_mk_agent.openwrt
Log Message:
-----------
11392 FIX heartbeat_crm: strict activation in agent
After werk #11042 pacemaker-controld is a target process required to
trigger the heartbeat_crm section in Linux and openwrt agents. The way such
process was found was susceptible to name collisions leading to the
discovery of fictuos services, because other processes on the same host
could be accessing the same service.
This werk makes it more strict to catalog only pacemaker-controld processes.
Problem being the "-f" option queries after all the parameters processes
are called. Other external software or other parallel running agent could
contain pacemaker-controld as argument and lead to activation of this agent
section.
SUP-4053
Change-Id: I97c8572ca3c38851512889f6dc0694662d4c92cd
Commit: c1c22be0adb17b2c5ad1f098894ce33d2354da0b
https://github.com/tribe29/checkmk/commit/c1c22be0adb17b2c5ad1f098894ce33d2…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2020-09-10 (Thu, 10 Sep 2020)
Changed paths:
M checks/cisco_fru_module_status
M checks/cisco_temp_sensor
M checks/entity_sensors
Log Message:
-----------
Cache some very long Description and Name entries
SUP-2550
Change-Id: I026307a43550f6e2ce76beb1c713338985db2124
Compare:
https://github.com/tribe29/checkmk/compare/e0aeb0a27424...c1c22be0adb1