Hi Guys,
We're experiencing a problem when attempting to disable certain hosts,
that they simply just don't disable.
The host exists in two separate hostgroups by itself (legacy reasons),
as well as existing in another hostgroup with other members.
hostgroup a
foo
hostgroup b
foo
hostgroup c
foo
bar
...having a look through the code, there seems to be an evil bit of
logic that will attempt to disable the hostgroup rather than the host
when ever the host exists in a hostgroup by itself. What's worse is it
appears it'll only attempt to disable the first hostgroup, ie in the
above example hostgroup a.
Is there any unusual dependencies I'll break if I remove this bit of
logic? Obviously any monitors will get called with no hosts, but I'm
fine with that - all the monitors we use will exit as they should after
checking nothing, so just a slight increase in load.
Any information would be greatly appreciated.
Cheers,
Ben
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
