Suggestions on the Nagios port

Hey folks,

        Many of you will breath a sigh of relief - I have decided to build Nagios normally, and worry about static/chroot at a later time (probably my first FLAVOR). :)

        However, Nagios is kind of a unique application - it's part web application, and part userland daemon. What I'm looking for is suggestions/direction on the directory structure to use. When I install Nagios from source, I typically install it in /home/nagios.

        I can hear the sharp intake of breath from here. ;)

        I _know_ that's not the OpenBSD way. Well, here's my dilemma:

${PREFIX}/etc = config files (about a dozen)
${PREFIX}/sbin = CGI's (about a dozen)
${PREFIX}/bin = nagios daemon
${PREFIX}/share = static HTML and images
${PREFIX}/libexec = Nagios plugins (next port on the agenda)
${PREFIX}/var = Nagios log files, PID file, command pipe that the

                          CGI's need to talk to, as well as Nagios daemon

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related openbsd.org Links advocacy announce bugs ipv6 misc ports ports-changes security-announce smp source-changes tech Request more information about Pantek

        ... that's the "typical" ./configure, make, make install for Nagios. Now, what is preferred/mandated within the OpenBSD ports tree? Should I split everything up amongst /usr/local (ie, CGI's in /usr/local/sbin, nagios daemon in /usr/local/bin, etc) ? Set PREFIX to be /usr/local/nagios (please don't kill me) ? Set PREFIX to /home/nagios like I normally do when I install from source? And if the preferred solution is to split it up into /usr/local, I assume the config files should end up in /usr/local/share/nagios/, and then copied to /etc/nagios ? Keep in mind, Apache's config is going to have to point at two of these directories.

        I'm just trying to avoid the typical faux pas and do things the way the porters say things should be done, rather than the way I have done them in the past. Also, since it's part CGI and part userland, this seems like a slightly different case than your normal piece of software.

Thanks!

Benny