From ArchWiki
Jump to navigation Jump to search

For use with lighttpd without htpasswd

Helped from the gentoo wiki I created a plain text /etc/nagios/passwd containing this line:


Then I used this config for setting it up with lighttpd (/etc/lighttpd/conf.d/nagios.conf):

$HTTP["url"] =~ "^/nagios" {
        alias.url = (
                "/nagios/cgi-bin" => "/usr/share/nagios/sbin",
                "/nagios" => "/usr/share/nagios/share" 

        $HTTP["url"] =~ "^/nagios/cgi-bin" {
                cgi.assign = ( "" => "" )

        #auth.backend = "htpasswd" 
        #auth.backend.htpasswd.userfile = "/etc/nagios/passwd" 
        auth.backend ="plain"    # The password is stored as plain text as user:password in...
        auth.backend.plain.userfile = "/etc/nagios/passwd"  # this file
        auth.require = ( "" => (
                "method" => "basic",
                "realm" => "nagios",
                "require" => "user=nagiosadmin" 

If anybody needs anything specific please indicate.

Webserver and other sub sections

Currently, the #Installation and other Configuration section are inside the #Webserver section. However, Nagios and PHP are not webservers, so it seems to me this subdivision is incorrect. I propose the following:

  1. Make "Installation" and "Configuration" level2 headings (with just "==" before and after the title text)
  2. Installation and configuration instructions be moved and subdivided inside them.
  3. Webserver information could be divided in (1) keep the current mention of optional but good for CGI (in #Webserver); (2) Installation of webserver, in the #Installation, mentions the options between Apache, Nginx, lighttpd and any other, but relying on main article's install instructions; (3) Configuration of webserver, in the #Configuration, mentions specifics and non-duplicated steps for Nagios.
  4. PHP likewise.

Any thoughts? -- Josephgbr (talk) 16:55, 11 November 2018 (UTC)

I'm not a user of the software so I can't contribute much, but that sure reads like a good plan to update the article and to bring it at par with a regular article structure to me. Regarding your step (3): The sections about Nginx & lighthttpd mainly consist of the configuration file. I saw that the package has an apache sample. Perhaps the package maintainer can add the other two configuration files as samples too, so that the article can link to them instead & is synced with the package somewhat more. Just an idea; perhaps makes it easier. --Indigo (talk) 10:58, 25 November 2018 (UTC)

Create a Plugins section

How about creating a Plugins section to hold information of each plugins? Currently there is a level2 heading #Plugin check_rdiff, but I was considering to add about NRPE too. -- Josephgbr (talk) 17:16, 11 November 2018 (UTC)

Sure, if you want to add another plugin, like NRPE, that's the straight forward structure for the section. It's no problem if you start it and mark the new plugin subsection with Template:Expansion, then take your time to work on it. Cheers. --Indigo (talk) 11:02, 25 November 2018 (UTC)