On 6 Feb 2006, at 20:48, Steve Shipway wrote:
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?
This is open source software. **We** are the development team :)
We've made a patch to include an issue_commands option to the
contacts definition to get this functionality. This has been done to
the 2.0 code. It is available here: http://www.altinity.org/
I'll submit to nagios-devel to see if Ethan will include it into the
main branches.
Ton
http://www.altinity.com
T: +44 (0)870 787 9243
F: +44 (0)845 280 1725
Skype: tonvoon
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users@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
