Figured it out. I made the mistake of believing the man page and doc in analysis.cfg.
FILE filename [color] [things to check] [TRACK]
Should read:
FILE filename [things to check] [color] [TRACK]
color needs to come after the checks. I happened to notice one of the examples used this and changed mine to use it and (surprise) my file test started working.
=G=
From: Root, Paul T <user-76fdb6883669@xymon.invalid>
Sent: Friday, December 13, 2013 9:59 PM
To: Galen Johnson; xymon at xymon.com
Subject: RE: [Xymon] File check question
You saying no exist not exist. The way I read it they are ANDs.
-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Galen Johnson
Sent: Friday, December 13, 2013 4:11 PM
To: xymon at xymon.com
Subject: [Xymon] File check question
Hey,
I have a question about file tests. The man pages say
FILE filename [color] [things to check] [TRACK]
I have a test defined as
FILE /tmp/ldap2pw.lck red NOEXIST MTIME>900
How does the "[things to check]" actually parse? Is it an "and" or an
"or"? In other words, would that read "the file exists AND hasn't been
modified for more than 15 minutes" or "the file exists OR hasn't been
modified for more than 15 minutes". I'm assuming "and"...actually I
need it to be "and" in this case. Or do I have to explicitly say
something like "NOEXIST and MTIME>900"? I can't find anything about that.
thx
=G=