I think that is what I found as well, so I bagged the class stuff
altogether and went with only host names. And I refreshed my memory on
how to cut and paste in my text editor...
GLH
-----Original Message-----
From: McGraw, Robert P [mailto:user-33cf07af04dd@xymon.invalid] Sent: Tuesday, July 22, 2008 12:37 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] FILE monitor and mtime<600 troubleshooting
Have you tried placing the lines at the very top of the file or at the
very bottom?
I had a problem with the client-local.cfg file where I had put the
hostname of the same class after the class name which was empty. Nothing
worked. Once there is a hit, hostname or class, it stops processing. So
it seems that you cannot expect hostname commands and class name
commands to both execute; which ever it finds first it executes those
commands and then stops. At least that is what I have found.
Robert
-----Original Message-----
From: Denver Osborn [mailto:user-379e8d8cd715@xymon.invalid]
Sent: Tuesday, July 22, 2008 9:08 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] FILE monitor and mtime<600 troubleshooting
Sorry if this is obvious but have you tried this using just the > HOST=hostname to make sure it is working?
Thanks, I did that and all works well with HOST=hostname. The one thing I couldn't get working is CLASS=classname. Using the CLASS=classname entry makes more sense for file monitoring as the same
file in different platforms vary in permissions and location. If I can't make it work with CLASS I'll stick with what works by
maintaining multiple HOST entries.
The configs once again are
# hobbit-clients.cfg:
CLASS=hpux11iv1
FILE /etc/sudoers mtime>600
# client-local.cfg:
[hpux11iv1]
file:/etc/sudoers
# bb-hosts
0.0.0.0 hpux_host # CLASS:hpux11iv1
-denver