We maintain everything on one central server and then use rdist to push them
out to the clients. I have one clientlaunch.cfg file which has everything in
it and all of the ext scripts test if they are running on the right host.
This could be done better, but we don't have enough monitored clients to
make it worth the extra effort.
If I was going to improve it I would have the clientlaunch.cfg file have m4
directives to select stanzas for the host being rdisted to (we actually us a
system called distrib built on top of rdist which does this automatically),
that way a single clientlaunch.cfg file would serve as the source for
multiple files on the various clients. The same system (distrib) would
control which clients got which ext scripts.
Steve.
---
On Wed, Dec 17, 2008 at 11:06 AM, Don Lachlan <user-32e83f32b5ed@xymon.invalid>wrote:
I have a number of custom scripts spread across multiple machines; I
understand how to configure them in clientlaunch.cfg but I would like
to keep them in a single config file (it's impractical to maintain
this many individual configs). Has anyone written a tool to manage
push/pull of the configs and generating individual hobbit-clients.cfg,
or otherwise duplicate what bb-bbexttab did?
-Lachlan