Am 27.04.2012 19:26, schrieb Michael Friedrich: > short update on that - the current r1.7 will now warn you when loading > idomod.o instead of idomod.so > question remains - should this just warn or bail out entirely refusing > to load the possible old module? I vote to rename or remove the older version. I ran for myself (and at least i should really know this) not only one time into trouble , because i added the new config to the modules dir, but forgot to remove the broker entry in icinga.cfg. This results in very funny errors in ido2db and it took some hours for me to track the problem down to this change. If we remove the old module it will leave a clear error message in syslog if the module is still configured, but could not loaded(because its removed) and indicates, the new configuration is not yet in place. This will help us to support if this this high potential error occurs after the release
Thomas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ icinga-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-devel
