>>> On 6/11/2008 at 4:28 PM, in message <[EMAIL PROTECTED]>, "Bernard Li" <[EMAIL PROTECTED]> wrote: > Hi Ulf: > > On Tue, Jun 10, 2008 at 1:49 AM, Ulf <[EMAIL PROTECTED]> wrote: > >> If I try to compile it without static-build I will get the error '0509-022 > Cannot load module /usr/lib/ganglia/modcpu.so' > > Have a look at your /etc/ganglia/gmond.conf: > > /* Each metrics module that is referenced by gmond must be specified and > loaded. If the module has been statically linked with gmond, it does not > require a load path. However all dynamically loadable modules must > include > a load path. */ > > So all you need to do is remove 'path' for each module and it should work. > > It would be great if we can omit path for each module for the default > gmond.conf if gmond is built with --enable-static-build so that users > will not shoot themselves in the foot. > > Brad, do you think this can be implemented? >
It is already suppose to be doing that. When lib/default_conf.h is processed from configure, it comments out all of the path statements in the default gmond.conf. This is done by setting the AC_SUBST variable 'modpathstart' during configure. Then when gmond.conf is generated by gmond -t >gmond.conf, all of the path statements should be commented out. So just by building gmond statically, the gmond binary should already have the switches in place to build gmond.conf correctly. Brad ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
