Den 2014-02-08 3:49, John Thurston skrev:
I've been using my Solaris BB clients with my Xymon server, but am
hoping the xymon client will be more zfs-aware than the ancient BB
client. To that end, I'm trying to compile a xymon client.
I've spent most of the day fighting with the 'make' process.
[snip]
The crazy part is when I compare the results of making with --client
and --server. I can only find one difference. A --client build has
created the application bin/xymond_client
There are two ways of running the client: In "server-side" mode, where all of the configuration and data analysis happens on the Xymon server, and "client-side" mode where you configure the client locally (the way BB does).
The "xymond_client" binary is the only difference between a client- and server-side configured client. "xymond_client" is the program that analyses the client data and generates the status updates, so when you configure the client for "client-side" configuration, then you get this extra binary. However, it also uses a lot of external libraries that you can avoid installing on all of the servers you monitor by using server-side configuration.
Client-side really is a hack, and it will probably be removed in v5. So I really do recommend that you use server-side configuration, to keep the client installation as dumb as possible.
Is this really the only difference? If so, why is there a broken
build process for the '--client' option? Why doesn't the '--server'
option also build the xymond_client and leave it abandoned in the bin
directory?
"configure --server" builds both the Xymon server programs and the Xymon client programs. The client programs end up in the "~xymon/client/" directory.
Building only the client with "configure --client" should work, but I'll readily admit that testing on Solaris is not at the top of my priority list. I haven't had reports that it is completely broken, though.
Regards,
Henrik