hi john, On Wed, Oct 12, 2005 at 11:10:18AM -0700, John Stile wrote: > The --with-default-perfdata seems to be needed to use nagios.conf > service_perfdata_command=process-service-perfdata. The > process-service-perfdata is used to send data to another program (like > the nagios-plugins nagiosgraph, apan, and perfparse). They glue rrdtool > to nagios. After messing around with the deb packaged nagios compiled > with -with-file-perfdata that my only nagios-to-rrdtool glue progam > would be perfparse, but it drove the load way too high. So > --with-file-perfdata, I'd need to write my own glue program. Like all > these open source projects, the glue-ability makes the base program more > powerful. My qmail setup is about 25 programs glued to qmail.
okay. well in the next upload of nagios, i'll see about changing the configure setting to use default-perfdata. would you happen to know if the options are exclusive of eachother, or if i can have them both on? > This is the thread I created, and down where says SOLVED, I show what I > had to do to get things working, though it was more 'the hacker way' > than the 'the debian way', it worked. > http://www.nagiosexchange.org/nagios-users.34.0.html?&tx_maillisttofaq_pi1%5Bsort%5D=mail_date%3A0&tx_maillisttofaq_pi1%5Bmode%5D=1 > > If there is a better debian way, it would be cool is to post 'the debian > way' to rebuild a deb package from the deb-source package to get > --with-default-perfdata. well i think the first step of the "debian way" in a situation like this is to report a wishlist bug and to see if you can get the maintainer to fix it, which should make everything else moot. when that fails, doing something like what you've done above isn't too bad of a way, albeit a bit fragile. something to make it a bit better would be to pin the nagios package so that you don't accidenally overwrite your compiled-from-source package. then when there's an update available, it will show up on the list of "updates that are held back", and you can upgrade the source package at your leisure. details for pinning are buried somewhere within apt_preferences, though you could probably find better documentation elsewhere (debian user manual, debian wiki, or maybe the debian-user list). it's also possible that apt-src may help managing installing from source, but i've never used it so ymmv. sean --
signature.asc
Description: Digital signature
