On Nov 5, 2009, at 11:32 AM, Darren J Moffat wrote: > John Fischer wrote: >> Interfaces >> ========== >> nagios user is created. Uncommitted. >> nagios group is created. Uncommitted. >> nagcmd group id created. Uncommitted. > > Why are two new groups needed ?
I saw this case go by and, as someone who makes daily use of nagios, I thought I'd make a comment or two which will hopefully be useful. The two groups are for abstraction between nagios the server and the jobs it performs on remote systems either via ssh or nrpe. One is for the daemon, one is for everything else that communicates with it. > >> /etc/apache2/2.2/nagios.conf -- Uncommitted. >> /usr/apache2/2.2/bin/<cgi-scripts> -- Uncommitted. The nagios.conf doesn't belong with the apache configurations as it's for the nagios daemon apart from apache. There is a cgi.conf which governs the behaviour of the cgis but it, too, would likely be best living with all the other nagios configuration files. And I agree on all the other filesystem convention comments. Also, in order to make use of the nagios dashboard/interface via apache, it has a dependency on mod_php, just in case that hasn't already been noted. I would also leave the embedded perl off as, in the most recent versions, it's easy enough to use most any scripting language you prefer for writing monitors/plug-ins and embedding perl is mostly unnecessary. e.
