From 1bbd9d629e9a4efaa816fc3411ad7272ad61636d Mon Sep 17 00:00:00 2001
From: Gunnar Beutner <gunnar.beutner@netways.de>
Date: Mon, 28 Jan 2013 08:31:29 +0100
Subject: [PATCH] Use check interval (rather than retry interval) when
 rescheduling passive checks.

---
 lib/icinga/externalcommand.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/icinga/externalcommand.cpp b/lib/icinga/externalcommand.cpp
index 04e18dd30..92db8a0a3 100644
--- a/lib/icinga/externalcommand.cpp
+++ b/lib/icinga/externalcommand.cpp
@@ -137,7 +137,7 @@ void ExternalCommand::ProcessServiceCheckResult(double time, const vector<String
 	/* Reschedule the next check. The side effect of this is that for as long
 	 * as we receive passive results for a service we won't execute any
 	 * active checks. */
-	service->UpdateNextCheck();
+	service->SetNextCheck(Utility::GetTime() + service->GetCheckInterval());
 }
 
 void ExternalCommand::ScheduleSvcCheck(double time, const vector<String>& arguments)