Hi Rolf,
In <4CE6358A.40908 at hebis.uni-frankfurt.de> Rolf Schrittenlocher <schritte at hebis.uni-frankfurt.de> writes:
seeming rather simple but I cannot find the solution. I'm monitoring some files with md5 checksum for changes. All those files had the same md5 on all servers: FILE /usr/bin/ps MTIME>600 MD5=facb1ea65094c87058df4f0ffdf7306a red
Now a new server has a different installation so I added him in hobbit-clients.cfg above the first entry: FILE /usr/bin/ps MTIME>600 MD5=76b66713137851c1407fd9ea20785bc0 HOST=<new host> red FILE /usr/bin/ps MTIME>600 MD5=facb1ea65094c87058df4f0ffdf7306a red
But for the check the old entry is used:
File has MD5 hash 76b66713137851c1407fd9ea20785bc0 - should be facb1ea65094c87058df4f0ffdf7306a
What happens is that when evaluating the data for "<new host>", BOTH of those lines will match. So the result ends up being the last one, which is that the MD5 checksum is not correct.
To avoid this, add an "EXHOST=<new host>" to the second FILE rule.
Regards, Henrik