bad news for you:
nagios keeps on checking the services and doesn't even check the host anymore ... (which can be a problem, btw!)
Here is a scenario:
-a service goes down on a host
- => nagios tests the host
- host is found DOWN => nagios notifies host DOWN
- nagios keeps on testing the services, and notifying HOST DOWN
- one service goes UP => the host is assumed to be UP => the HOST UP notification is sent
it has some logic, especially knowing that (apparently - I don't know why), host checks are more ressource consumming than service checks (host checks are not scheduled, so they have to be inserted in the plan).
Hope this is clear enough
btw: my problem is that, even if the host goes UP (machine is restarted) but no service is UP (process monitored not restarted, or NRPE not restarted), nagios won't detect that the host is up and will still notify the HOST DOWN alert ... which is really stupid and confusing for the team that reads the alerts.