Marcel
I copied the aix_memory check from innovation release tarball and
dropped it in our local check path. Again we’re at version 1.2.4p5.
It is now shown as installed:
OMD[devl]:~$ check_mk -L | grep memory
aix_memory tcp yes yes Memory used
user@check_mk[/tmp/check_mk-1.2.5i6p4]$ ls -ltr
/omd/sites/devl/local/share/check_mk/checks
total 12
Yet we are not getting any output when doing "check_mk -d aix_host |
grep memory." Same with “check_mk --checks=aix_memory -I aix_host.”
Do I need “mem.include” in the same path as “aix_memory?” I am
guessing that’s a dependency of some kind.
Do you have any ideas on how to proceed? I tried following this guide:
https://mathias-kettner.de/checkmk_devel_agentbased.html
Thanks
Doug
Thanks
Douglas Charles Duckworth
Unix Administrator
Tulane University
Technology Services
1555 Poydras Ave
NOLA – 70112
E: duckd@tulane.edu
O: 504-988-9341
F: 504-988-8505
On 12/05/2014 02:14 PM, Marcel Schulte wrote:
Mathias expects next stable (maybe 1.2.6) to be released in
February. But who knows, if we stay well-behaved… maybe it
becomes a gift under the tree?

Marcel
Duckworth, Douglas C <duckd@tulane.edu mailto:duckd@tulane.edu>
schrieb am Fr., 5. Dez. 2014 21:03:
Danke Marcel
Do you know when we can expect another stable release? I am unsure
if we can run unstable code in production despite the high
frequency of commits.
Best Doug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJUhdP5AAoJEP/Xbmk1axQpbZcQAKBPxKqHknkihmpPEBLiPxce
sixlmp1GtZfYpFrY9X5IdOAkRlOD65KLZNuGsXGub2R/SVvd9Y5dM/yE0rstz6Ly
qxj/pdDBqP0yBwvtvNkUm4AAJF0Cv4xTP6dExDvTFK6+g565prQ+X/473bEzVm6Q
pk7+W0gi3SpR090lKIDaM+37mQpZrUYsqu2r5Kc6Rkk61qMSvFoTKmzzF1JpE/tf
ZldpW+WNVHsrPglvkLqcV2+8RJdOIN4vq1GNuMOz3TuYi373aVJ7MGTjRVBHkDsu
bMpqLi+MtIgTbbehua5yRQ4i8WP2u7TCOuVkjmFuF1UklZwRD3KYTwrdVahhCYSU
f291HA+zmuxUBWDohyGuYrAaAfXUK03XpD+menrIhwyNKJrNFT2HYLZIFxJwqjeS
vA3FFItORxXh27Co40c6NSmYn0QtLQkh8k2s2ki1tJH+gdCEsYYqwCV9+MZaJ8fZ
UBth8bne4biq78K+5NHyLVF+IAtYtLQqZHtrj5xy33wR1TWTEPf0CcvcCAW6BSkX
nZqRrfgrmCrNsnuuqJtI503/FayCCcx9EKg1d++DFrvC6JFePReKj1pf1xHZjdrp
9IfOYRCajhfBqvUFJGb5u4JMm6zl6TB657VFb16NpB3ug2XNWdnXrHCbtEBmOdg/
AOM3HAYvJLlU+LTkqJcY
=YmeG
-----END PGP SIGNATURE-----