Reporting and misc rave.

[Steve Shipway]

Ton Voon wrote:
> On 3 Feb 2006, at 19:24, Tedman Eng wrote
> > Read/Write access to cmd.cgi can already be disabled using .htaccess
> 
> I tried that (setting a group in .htaccess and only certain 
> users into that group), and it worked, but I didn't like the 
> user experience 

This is the same reason we don't do it this way.  I would definitely like a
'issue_commands=' option for a contact, since we don't need to have any more
granularity than that (eg, read this service, admin that one...)

I'm currently wary, though, of making too many (any) modifications to Nagios
1.2 code when 2.0 is just around the corner.  Too many site customisations
mean an inability to upgrade.  Prehaps this sort of thing can be submitted
to the 2.0 development team?

Steve




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null