I too wish the wildcard would work in client-local.cfg, or maybe the "include" directive. I'm adding about 2000 systems this year..

Ralph Mitchell On Jan 27, 2014 11:13 AM, "Galen Johnson" <Galen.Johnson at sas.com> wrote:

1. Well...poo! That's unfortunate as we have several dozen of similarly named servers we need to run some specific file checks on and it's going to be a bit annoying to have to add each one individually.

2. I'm concerned about having to use a command to find certain files..."If you want to check multiple files using a wildcard, you must use a command to generate the filenames. Putting wildcards directly into the file: entry will not work." Which would imply that if I want to check for a files using a wild card, I would need to have a line in client-local.cfg like:

file:ls /path/to/<pattern>

=G=

---

From: Mike Burger <mburger at bubbanfriends.org> Sent: Monday, January 27, 2014 10:35 AM To: Galen Johnson Cc: xymon at xymon.com Subject: Re: [Xymon] client-local.cfg

...

Hey,

I have a couple of questions regarding the client-local.cfg file.

1. can it handle reg-ex for hostnames like other cfg files? For example, [%(myhost1|myhost2).*]

2. According to the man page for client-local.cfg, "When clients connect to the Xymon server to send in their client data, they will receive part of this file back from the Xymon server." What if you are using xymonfetch? Would I need to create a local client-local.cfg file within the .../xymon/client/etc folder?

1. Already ran through this (even asked on this list)...no...no regexp for the hosts in client-local.cfg.

2. Use the client-local.cfg file on the server in $XYMONHOME/etc (or, if you installed via rpm, /etc/xymon. I do have a couple of systems where I'm using xymonfetch, and it's pulling data, including log info and such, without any issues.

-- Mike Burger http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

1. even with the include, you have to define each host entry.

2. No more concerns. My concern was around using xymonfetch and that the server sent some info for the files. Mike (and experimentation) has removed those concerns.

=G=

From: Jeremy Laidman <jlaidman at rebel-it.com.au> Sent: Monday, January 27, 2014 11:02 PM To: Galen Johnson Cc: Mike Burger; xymon at xymon.com Subject: Re: [Xymon] client-local.cfg

On 28 January 2014 02:57, Galen Johnson <Galen.Johnson at sas.com<mailto:Galen.Johnson at sas.com>> wrote:

1. Well...poo! That's unfortunate as we have several dozen of similarly named servers we need to run some specific file checks on and it's going to be a bit annoying to have to add each one individually.

You could make this easier by having an include file. Then just include the file for each host:

[server1.example.com<http://server1.example.com>] include standard-client.cfg [server2.example.com<http://server2.example.com>] include standard-client.cfg

Not as good as regexp or wildcard hostname matching, but slightly better.

Another option is to auto-generate your client-local.cfg file from a macro configuration file - dare I say in M4 format? This is often how sendmail configurations are managed. After each change, you type "make" and it rebuilds the configuration file.

2. I'm concerned about having to use a command to find certain files..."If you want to check multiple files using a wildcard, you must use a command to generate the filenames. Putting wildcards directly into the file: entry will not work." Which would imply that if I want to check for a files using a wild card, I would need to have a line in client-local.cfg like:

file:ls /path/to/<pattern>

Correct. This works, and is awesomely extensible. What's your concern?

J