Nagios core does not require apache to run. Especially if it is in a distributed setup. The dependency on apache should be removed.
I'll see what I can do about making it work on apache free nodes. Might take me a few days, but I'm pretty sure I'll get it working for you.
Created attachment 14323 [details, diff] USE gd and apache2 flags For gd, use = "gd" which includes apache. For apache2, use = "gd apache2". Otherwise, default will install without graphical.
just to pitch in my support for removing the apache dep on nagios. It limits the usefullness of nagios if all client machines are required to have apache installed in order to monitor their processes, disk space, etc.
Would be nice to give some output (warning) when emerging nagios that you will need the USE flag gd if you want to have the url http://localhost/nagios/ working. Without this flag, the nagios components are not copied into the apache directories. It isn't such a big deal but may prevent users from scratching there bold head why the apache/nagios isn't working
hey all. The way the package currently works is that 'use apache2' changes the apache conf settings, which is pretty much what is expected. 'use libgd' on the other hand, is highly non-sequitor. If use libgd is absent, the ebuild installs nagios as normal with make fullinstall and install-conf, and then recursivly deletes the /usr/local/nagios/{share,sbin} (html and cgi) directories it just built. This behavior is non-intuitive since none of the cgi's actually depend on libgd to operate. The only two cgi's that use libgd are alert histogram and status map, and they will work without it, they just wont look very pretty. There is no logical explaination I can think of for deleting the html files based on the absense of libgd as they of course do not need it. In other words, making the installation of the html and cgi files contingent on libgd is silly, and is causing headaches. Please figure out some other way to detect if the user wants the web front end.
Created attachment 20950 [details, diff] determine if apache is installed, install fe if yes We could check /var/db/pkg to see if apache has been installed, and use that as criteria for installing the front end. This is probably not the way gentoo developers want to do things, and just having apache installed doesn't necessarily mean you want a nagios fe, but it's better than libgd for a criteria, and I didn't find anything in the developer docs specifically saying it was a no-no.
the ebuild is in cvs
Sorry to bark in like this, but I just had to do this. Suddenly I had a irristable itch I just _had_ to scratch. You can find nagios-1.1-r5 on the mirrors shortly. I have introduced a "noweb" local USE flag. If that flag is set no HTML/CGI will be installed. I also added a metadata.xml to it, stating that I'll take the fame and blame for the meantime until someone else steps up to take propper care of it.
Can't take ownership and close the bug at the same time...
