global event handler external commands not working

[Geoff Franks]

I'm trying to use the CHANGE_GLOBAL_SVC_EVENT_HANDLER and
CHANGE_GLOBAL_HOST_EVENT_HANDLER external commands to modify the event
handlers on a nagios server without restarting the nagios process. As
far I can tell, I'm using them properly as defined in
http://old.nagios.org/developerinfo/externalcommands/commandinfo.php?com
mand_id=103 . However, it doesn't seem like the command actually changes
the global event handlers. Anyone know why this would happen? Am I using
it wrong? Is the feature not really supported currently?

Nagios 3.2.0

Nagios.log:
[1295474822] GLOBAL SERVICE EVENT HANDLER:
server1.test.com;tcp_nsca;CRITICAL;SOFT;1;process-standby-event
[1295474852] GLOBAL SERVICE EVENT HANDLER:
server1.test.com;ssh_nagios_latency;UNKNOWN;SOFT;1;process-standby-event
[1295474852] EXTERNAL COMMAND:
CHANGE_GLOBAL_SVC_EVENT_HANDLER;process-service-nsca-multi
[1295474852] EXTERNAL COMMAND:
CHANGE_GLOBAL_HOST_EVENT_HANDLER;process-host-nsca-multi
[1295474882] GLOBAL SERVICE EVENT HANDLER:
server1.test.com;tcp_nsca;CRITICAL;SOFT;2;process-standby-event
[1295474902] GLOBAL SERVICE EVENT HANDLER:
server2.test.com;check_lighttpd_status
NO_MINIMUMS;OK;HARD;3;process-standby-event

Geoff Franks
Monitoring and Reporting Engineer
Synacor, Inc.
40 LaRiviere Dr. Suite 300 | Buffalo NY 14202
Office: 716-362-3765



------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
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