<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 30 July 2015 at 00:54, Root, Paul T <span dir="ltr"><<a href="mailto:Paul.Root@centurylink.com" target="_blank">Paul.Root@centurylink.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2x6" class="a3s" style="overflow:hidden">I think you want /var/core/core.* in the client-local.cfg<br>
<br>
It's regex not just wildcard, so you need the . to stand for anything and * is 1 or more.<br></div></blockquote></div><br>I'm pretty sure it's not a regex for the term in backquotes - the string is simply given to /bin/sh to execute.  Can you test yours by creating a core file?</div><div class="gmail_extra"><br></div><div class="gmail_extra">I think the real problem is that the NOEXIST test won't even be executed when there are no files, because there's no file to test against.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Consider if I wanted to test for the existence of /tmp/badfile, and go yellow if it exists.  In client-local.cfg I would have:</div><div class="gmail_extra"><br></div><div class="gmail_extra">file:/tmp/badfile</div><div class="gmail_extra"><br></div><div class="gmail_extra">In analysis.cfg, I would have:</div><div class="gmail_extra"><br></div><div class="gmail_extra">FILE %^/tmp/badfile YELLOW NOEXIST</div><div class="gmail_extra"><br></div><div class="gmail_extra">This should work just fine.  Now consider if I updated client-local.cfg to look like this:</div><div class="gmail_extra"><br></div><div class="gmail_extra">file:</div><div class="gmail_extra"><br></div><div class="gmail_extra">Now, what will happen?  The Xymon client will have no files to report, and so there will be nothing relevant in the client data.  Therefore the entry in analysis.cfg has no filenames to match on, and so won't even try.  The fact that there's no filenames to test means that the file check goes blank, reporting that the file check has not been setup yet.</div><div class="gmail_extra"><br></div><div class="gmail_extra">By including a backtick expression that gives an empty result, you're producing an outcome that you weren't expecting.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I think what might give what you need is something like this:</div><div class="gmail_extra"><br></div><div class="gmail_extra">FILE:`ls -d /var/core; ls /var/core/core*`</div><div class="gmail_extra"><br></div><div class="gmail_extra">When there are core files, the result of this will be as if you configured:</div><div class="gmail_extra"><br></div><div class="gmail_extra">FILE:/var/core</div><div class="gmail_extra">FILE:/var/core/core91234</div><div class="gmail_extra">FILE:/var/core/core2244</div><div class="gmail_extra"><br></div><div class="gmail_extra">And the line in analysys.cfg will match two of them, so YELLOW.</div><div class="gmail_extra"><br></div><div class="gmail_extra">When there are no core files, the result will be as if you configured:</div><div class="gmail_extra"><br></div><div class="gmail_extra">FILE:/var/core</div><div class="gmail_extra"><br></div><div class="gmail_extra">And the line in analysis.cfg will not match, so GREEN.</div><div class="gmail_extra"><br></div><div class="gmail_extra">It's green rather than clear because there is at least one "[file:]" section in the client data against which the line in analysis.cfg can match.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Hope that helps!</div><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers</div><div class="gmail_extra">Jeremy</div><div class="gmail_extra"><br></div></div>