rename nagios to naemon in perl tests

this tests are all about naemon...
No functional changes, only cosmetic.

Signed-off-by: Sven Nierlein <sven@nierlein.de>
add test case for issue #68

this test ensures duplicate services are detected as warning.
Remove scheduling_info struct

The scheduling information structure contains lot of information and
statistics about the the current configuration, such as amount of hosts
and services.

There are a couple of problems with this struct however. Since the
scheduling is simplified/randomized, the inter-check delays isn't
really anything to bother about. The amount of hosts and services can
easily be mined out either from the cfg-files with tools, or by using
livestatus on a running system (recommended). Also the timings about
upcoming checks can be mined out through livestatus, possibly by
implementing a check for it, so the information actually can be graphed
and monitored.

The problem with the scheduling_info is however how it's implemmented.
One great goal for refactoring naemon would be to isolate its modules,
so the code doesn't look like spaghetti. The wproc module has already
been refactored to remove dependencies to lot of other parts, by
presenting an interface with callbacks. The event module depends on
everything, more or less. And everything depends on the event module.
The nature of the scheduling_info struct is that it needs to be
maintained in lot of different parts of the system, which is possible
in event module at the moment, but makes it impossible to move the
check execution handling out of event.c.

Removing scheduling_info struct will make it lot easier to refactor
event.c to make naemon lot more modular.

Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Remove test_scheduling

Test scheduling is basically a feature to analyze the scheduling_info
struct, which was a bad idea, as said in previous commit message. It
was also used to analyze timings for loading configuration, which there
is another API for already (there are lot of timing_points in the code,
use naemon -T to display).

So this is basically a cleanup to remove redundant timing analysis
features, which just adds lot of noise to the code.

Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Remove event type statistics tracking

Since the goal is to refactor the event queue to not know about
different event types, but just one type, which is a callback type, we
can remove the tracking of counts for different event types.

Next step should be to move per-module specific logic out to the
different modules. The method should_run_event() would be a good target
for next step.

Signed-off-by: Max Sikstrom <msikstrom@op5.com>