Well, I use HOST=hostname in hobbit-client.cfg instead of CLASS=classname, and then in client-local.cfg I use [hostname] instead of classname. And it works on my Solaris 9 systems.
One caveat is that the Hobbit agent must be able to read the file -- is /etc/sudoers readable?
Finally, you can look at the client data returned by the agent for this host and see what is being returned for these files. This can help you decide whether the problem is in the client-local.cfg part (which tells the remote agent what to watch) or the hobbit-client.cfg (which tells the server what to do with the data returned by the the Hobbit agent).
GLH
From: Denver Osborn [mailto:denver at fni-stl.com]
Sent: Friday, July 18, 2008 7:36 AM
To: hobbit at hswn.dk
Subject: [hobbit] FILE monitor and mtime<600 troubleshooting
Hi,
I'm running Hobbit 4.2.0 with the allinone patch on hpux and
can't get the FILE monitor to work. I've added the required file: entry in the client-local.cfg for the host, then put the FILE directive in the hobbit-clients.cfg file. After adding the monitor, the BBDISPLAY picks up the new file and shows it as 'green'. When testing the monitor by changing the mtime of my file, hobbit doesn't alert on the change.
Here's my hobbit-client.cfg entry:
CLASS=classname
FILE /etc/sudoers yellow mtime<600
The client-local.cfg entry:
[classname]
file:/etc/sudoers
Has anyone else seen this before or have any advice on how to
troubleshoot?
Thanks,
Denver Osborn